Software Development Process
 
::Home
::Software Process Model
::Current Standards for SW Dev
::User Need Assessments
::Concept Generation/Selection
::Specification
::Prototyping
::Maintenance
::Management Issues
 
::Game Development
 
::Paper Archive
Specification

  • Concurrent Software Development -- Joseph Blackburn, Gary Scudder, andLuk N. Van Wassenhove
    • Since instability of requirements specifications is a major problem, CSE can address this with simultaneous development of hardware and software requirements.
    • As with stage overlap, two-way high bandwidth information transfer can provide early detection of interface problems. This may not, in itself, decrease the frequency of quality problems, but it can reduce their severity by locating them closer to the source and preventing the "spread of infection" throughout design.

  • Turn Customer Input into Innovation-- Anthony W. Ulwick
     
  • Validation, Verification, and Testing of Computer Software -- W. R. Adrion, M. A. Branstad, and J. C. Cherniavsky
    • The adequacy of the requirements, that is, their correctness, completeness, and consistency, must be thoroughly analyzed, and initial test cases with the expected (correct) responses must be generated. The specific analysis techniques that can be applied depend upon the methodology used to specify the requirements. At a minimum, disciplined inspection and review should be used, with special care taken to determine that all pertinent aspects of the project have been stated in the requirements. A determination of the criticality of software quality attributes and the importance of validation should be made at this stage.

  • Knowledge-Based Software Design Using Design Schemas -- Mitchell D. Lubarst, Mehdi T. Harandi