csus logo
FIRST ANNUAL CONFERENCE ON QUALITY SOFTWARE DEVELOPMENT
Friday, October 10, 2008
7:30 AM to 4:30 PM
Foothill Suite - University Union

CALL FOR PRESENTERS
Immediate response requested!

BACKGROUND. Software is playing an ever-increasing role in our day-to-day lives. Unfortunately, software systems often fail to deliver as promised. It is widely known that unresolved errors remain in many software systems that we are using every day.

OBJECTIVE. We wish to create a forum for the greater Sacramento area to bring software development professionals from business, industry and government together to discuss the current practices and challenges in quality software development. Ultimately, we hope to benefit software engineering education.

The inaugural CSUS Software Engineering Conference will provides a forum for individuals and organizations seeking technologies, concepts, and methodologies to improve the quality of their software products, processes, and services, and looking to enjoy networking and learning opportunities.

WHY ATTEND THIS CONFERENCE?

  • To learn proven methods and techniques for software engineering, quality and project management that others in the Sacramento region are using to achieve software excellence.
  • To network with your peers to compare successes and challenges
  • To increase your productivity by implementing the tools and techniques presented
  • To participate in tutorials that will provide you with new skills to enhance your working processes
  • To learn about new tools and products provided by exhibitors

CALL FOR PRESENTERS. The Software Engineering Faculty Group in the Department of Computer Science is soliciting proposals for presenters on various aspects software development that inform attendees about issues and practices affecting the delivery of quality software. The format for this conference will include a variety of sessions with individual presenters, co-presenters or panel discussions. Suggested Topics of Interest are listed below. Sessions will run approximately 45 minutes and include the presentation and follow-up discussion.

Interested parties should provide the following information:

(* denotes a required field)
* Name
* Job Title
* E-mail
* Company Name
* Street Address
Building / Floor / Room / Suite #:
* City
* State
* ZIP Code
* Phone
* Description of the proposed presentation

 
Special requirements for the presentation

 

Select your area of interest and we have some suggested topics you might interesting to present on:

TOPICS OF INTEREST:

REQUIREMENTS ENGINEERING
SOFTWARE DESIGN
VERIFICATION, VALIDATION AND QUALITY ASSURANCE
PROJECT MANAGEMENT

Each submission will be reviewed and submitting parties notified.

 


REQUIREMENTS ENGINEERING. Done well, requirements engineering presents an opportunity to reduce costs and increase the quality of software systems. Done poorly, it could lead to software cost overruns, customer dissatisfaction, and software project failure. Many software project failures have been attributed to requirements engineering issues. These include poorly documented requirements, requirements that were impossible to satisfy; requirements that failed to meet the needs of users, and requirements creep.

Topics of interest include, but are not limited to:

  • Requirement analysis and elicitation techniques
  • Requirements specification - one way or many ways
  • Requirement traceability and change control processes
  • Requirement analysis modeling (use cases, sequence diagrams, etc.)
  • Requirement validation and evaluation
  • Modeling Non-functional Requirements
  • Reusing Requirements and reusability


SOFTWARE DESIGN. From a requirements specification to a software product, software design plays an important role in identifying and defining software elements/components, their externally visible properties, and the interactions among them. To succeed you need techniques that facilitate the creation and analysis of system designs, the communication between software architects and stakeholders, as well as the communication between software architects and implementation teams.

Topics of interest include, but are not limited to:

  • Design tactics for non-functional quality attributes (e.g., availability, security, modifiability, usability)
  • Software architectures design patterns (e.g., service-oriented architecture, multi-tier architecture)
  • Object-oriented design patterns (e.g., creation patterns, structural patterns, behavioral patterns)
  • Design notations (e.g. UML)
  • Software design reuse and product lines
  • Software design analysis and evaluation


VERIFICATION, VALIDATION AND QUALITY ASSURANCE. The software V&V process is tightly integrated with the software development process. For each activity in software development there is a corresponding software V&V activity to verify or validate the products of those activities. Software V&V includes activities to determine that the software system performs its intended functions correctly, to ensure that it performs no unintended functions, and to asses the software quality attributes such as reliability, security, usability, efficiency, and maintainability.

Topics of interest include, but are not limited to:

  • Software V&V management
  • V&V traceability analysis
  • Test-driven development
  • Test automation
  • Model-based testing
  • Code review and inspection
  • Test oracles
  • Object oriented testing
  • Measuring testing progress


PROJECT MANAGEMENT. Software development projects are typically fast-paced, with customers that are more demanding, less patient, and with less tolerance for software that does not work. Practices that may have worked on previous projects often do not work on current projects. There is no one "best practice" for managing projects. Consequently, project managers are continually faced with a challenge to deliver software on time and within budget and yet still provide customers and users with quality software that meets their needs.

Topics of interest include, but are not limited to:

  • Project lifecycle management to fit the project
  • Risk management
  • Teamwork
  • Technical reviews
  • Realistic and usable work breakdown scheduling and control
  • Estimating and scheduling the work
  • Managing meetings
  • Assessment, process improvement and what to measure


Sponsored by the Department of Computer Science,
College of Engineering and Computer Science

The Software Engineering Faculty Group:

Professor Bob Buckley
buckley@csus.edu

Professor Ahmed Salem
salema@csus.edu

Professor Cui Zhang
Graduate Program Coordinator
zhangc@csus.edu

Co Sponsor
IEEE Sacramento Valley Section