Process - Introduction to Software Engineering | CS 3300, Exams of Software Engineering

Download Process - Introduction to Software Engineering | CS 3300 and more Exams Software Engineering in PDF only on Docsity! 1 PROCESS (Pass 1) GA Tech CS 3300 AY 2002 Fall 2001 next chapter: Plan development process Plan configuration management - how to manage documents & code - document: SCMP Plan quality assurance - how to ensure quality - document: SQAP Integrate & test system Analyze requirements Design Maintain Test unitsImplement Software Engineering Roadmap: Chapter 1 Focus Identify corpor- ate practices - assess capability - specify standards - e.g. CMM level Development phases Plan verification & validation - verify the product satisfies requirements - validate each phase by showing it succeeded document: SVVP Plan project Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. Chapter Learning Goals • Distinguish among development processes – Indicate benefits and disadvantages • Define software “quality” quantitatively – Institute collection • Understand documentation needed – Approximately one for each waterfall phase – Plan for configuration management Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. • Stand-alone – residing on a single computer – not connected to other software or hardware – e.g., word processor • Embedded – part of unique application involving hardware – e.g., automobile controller • Realtime – functions must execute within small time limit • typically microseconds – e.g., radar software • Network – consist of parts interacting across a network – e.g., Web-based video game Some Application Types Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. Typical Project Roadmap 1. Understand nature & scope of proposed product 2. Select the development process, and create a plan -- section 4 and chapter 2 4. Design and build the product -- chapters 5, 6, and 7 6. Deliver and maintain the product -- chapter 10 3. Gather requirements -- chapters 3 and 4 5. Test the product -- chapters 8 and 9 Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. Structured Programming Function definition handleAccount(…) getDetailsFromUser(…) getAccount(…) doTransaction(…) …… Function definition getDetailsFromUser (…) getName(…) …... Function definition getAccount(…) getFirstName(…) …... …... TOP DOWN Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. 2 Object Orientation Real world concepts Software design entities Skljkvjkvjfkavjafkk saovjsdvjfvkfjvkfjk Skljkvjkvjfkavjafkk saovjsdvjfvkfjvkfjk Skljkvjkvjfkavjafkk saovjsdvjfvkfjvkfjk Skljkvjkvjfkavjafkk saovjsdvjfvkfjvkfjk Account getDetails() Transaction execute() Customer getFirstName() Direct correspondence Graphics reproduced with permission from Corel.Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. The COM Idea Identification interface getName() setName() getSSN() setSSN() Computation interface Asset interface account COM object Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. Five Key Expectations (Humphrey) Influenced by people Used for process development Part of the project Aspect of the product 3. Keep all work visible 5. Measure quality 4. A. Design only against requirements B. Program only against designs C. Test only against requirements and designs 1. Predetermine quantitative quality goals 2. Accumulate data for subsequent use Artifacts and Roles Artifacts: the entities that software engineering deals with. Document Model -- a view of the application (design etc.) Component -- physical (source code etc.) Workers: responsibilities allocated to people (roles). USDP term Symbol & examples Worker Worker instance (e.g., Joe Smith) Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. The Waterfall Model Requirements analysis Design Implementation Integration Produces … specification (text) ... diagrams & text ... code & comments ... entire code Test... test report, including defect descriptions Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. More Detailed Waterfall Version Design Implementation & unit testing Integration System testing Concept analysis Analysis Maintenance Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.