32 PARTI ducton te Stem Develpent of domain classes, You could document this wi tion in lists, but diagrams provide a visnal repree tion that is often casier to remember and wnderand These activities support Core Proces k Discever an to help Warne keep track of all his gencachine e caching activities In this end-of chapter case, you will go through the various core processes of an SDLC And pertors some of the activities of a development projes project is divided into days as s our Tradeshow System projece. The daily assignments for this case should be considered as peeliminary efforts and rough drafes. The objective of these assignments is to he you remember the overall aperoach to software devel opment. Several assignmenes have been listed for each day to allow your instructor to selest those that best meet the objectives of the course. understand derails. Assignment D2-1: Identify a fow usu cases tha apply to one subsystem. Hint Think of wh Wayne plans to do with the system He w the systom to "do what"? klered as preliminary effoers and rough Assignment D2-2: Try to identify the classes that apply to the first project iteration. [Hint Think o "information things that Wayne wants the sys term to "remember Day 0: Define the Vision Assignment D2-3: Create a simple use case dia gram from the list of use cases. Hint Drawing by hand is fing, Use the one in this chapter as a Either by yourselt or with another class membe brainstorm all the functaons this reocaching syste might do. Keep it at a very hach level. These activities closely relate to Core Process I Identifv problem amd obtain approval. model Assignment D2-4: Create a simple class diagram from the list of classes. THint: Drawing by hand fine. Use the one in this chapter as a model. Tu of other infarmation that applies to each class i Assignment DO-1: Write a rough draft of the System Vision Document based on your brain- storming ideas. Hint: Think of what Wayne wants e system to do and why this heles him.) Day 3: Define the User Experience Day 1: Plan the Project These activities are a continuation of what you he gan in Dav 2. The objective here is to further de what Wayne will need and how he will actually the system. You will determine exactly how each ue case works-what steps and options are availabe with the use case and even what the display and da entry screens will look like. These activities priman ily support Core Process 3: Discover and undersn details. Based on the scope and vision vou described in the System Vision Document, divide the project into at least two separate subsystems that can be done in sepa- rate iterations. For example, perhaps a first version can run on a laptop, with a second version that includes mobile components for a smartohone, These activities are related to Core Process 2: Plan and monitor the project-whar to do, how to do it, and who does it. Assignment D1-1: Divide the system into at least two separate components or subsystems, which can be supported with two iterations. Briefly de- scribe each. Assignment D3-1: Select a single use case and identify the steps required to perform the use case. (Hint: Think of what Wayne does and how the system responds. Assignment D1-2: Create a work breakdown structure that lists all the steps to complete the first iteration. Put a time estimate on each step. (Hint: Use the one in this chapter as a model. Assignment D3-2: Make a workflow diagram of the selected use case. [Hint: Drawing by hand is fine. Each step from D3-1 goes in an oval. Connect the ovals with arrows.] Day 2: Define and Understand the Requirements Assignment D3-3: Sketch out one of the screens that will be required to support a use case. The screen should allow for data entry and display of information. (Hint: Don't make it elaborate. Focus only on the input and output data fields that apply to only one use case. On Day 2, you want to get an overall view of what the system needs to do for Way ne. There are two pri- mary areas to focus on to obtain this high-level un- derstanding of the system: a list of use cases and a list CHAPTER 1From Beginning to End An Overview af Systens Analysis and Design 33 Day 4: Develop the Software Architecture Design The high-level software architectural design of the SYstem generally includes decisions about how the sys- rem will be built and what the databasse will look like. Design is a technical activity that requires experience in programming, database development, and software architecture. These activities support Core Process 4 Design system componets. you prefer. For this answer, draw on your previ- OUR programming and development experiences. THint: There are marny valid solutions. Give rea sons for your preference. Day 6: Test and Deploy the System You may have had opportunities to perform compre hensive testing of your programming class projects, especially if you have developed systems that inte- grated with other systems. These activities support Core Process 6: Complete system tests and deploy solution. Obviously, you can only do this if you have programmed the system. Assignment D4-1: Design a preliminary database schema for the classes in this iteration. [Hint: Each class becomes a table, The attributes be- come table columns. Assignment D6-1: Write a paragraph describing the difforence between programmer testing and user testing. (Hint: Why is it hard to test your own work? What do the users know that you don't know? Assignment D4-2: Decide whether you will build a desktop system or a browser-based system. Write a couple of paragraphs listing the pros and cons of each alternative to defend your decision. (Hint: Either option is valid. Think of reasons to support your decision.) Assignment D6-2: Write a paragraph describing all the issues that might need to be addressed to deploy this system, Hint: You might want to search the internet to learn about deployment issues.) Day 5: Develop the Detailed Design and Program the System You probably have had many class projects where you designed a system and then programmed it. These kinds of activities support Core Process 5: Build, test. and integrate system components. Assignment D6-3: Look at www.geocaching.com, which is a commercial Web site. What other issues need to be addressed to deploy this type of Web site? Hint: Think about all the issues related to se curity, robustness, financial protection, high vol- Assignment D5-1: Write a paragraph describing what programming languagels) you would rec- ommend and what development environment umes, uptime, different browsers, and so forth.] 32 PARTI ducton te Stem Develpent of domain classes, You could document this wi tion in lists, but diagrams provide a visnal repree tion that is often casier to remember and wnderand These activities support Core Proces k Discever an to help Warne keep track of all his gencachine e caching activities In this end-of chapter case, you will go through the various core processes of an SDLC And pertors some of the activities of a development projes project is divided into days as s our Tradeshow System projece. The daily assignments for this case should be considered as peeliminary efforts and rough drafes. The objective of these assignments is to he you remember the overall aperoach to software devel opment. Several assignmenes have been listed for each day to allow your instructor to selest those that best meet the objectives of the course. understand derails. Assignment D2-1: Identify a fow usu cases tha apply to one subsystem. Hint Think of wh Wayne plans to do with the system He w the systom to "do what"? klered as preliminary effoers and rough Assignment D2-2: Try to identify the classes that apply to the first project iteration. [Hint Think o "information things that Wayne wants the sys term to "remember Day 0: Define the Vision Assignment D2-3: Create a simple use case dia gram from the list of use cases. Hint Drawing by hand is fing, Use the one in this chapter as a Either by yourselt or with another class membe brainstorm all the functaons this reocaching syste might do. Keep it at a very hach level. These activities closely relate to Core Process I Identifv problem amd obtain approval. model Assignment D2-4: Create a simple class diagram from the list of classes. THint: Drawing by hand fine. Use the one in this chapter as a model. Tu of other infarmation that applies to each class i Assignment DO-1: Write a rough draft of the System Vision Document based on your brain- storming ideas. Hint: Think of what Wayne wants e system to do and why this heles him.) Day 3: Define the User Experience Day 1: Plan the Project These activities are a continuation of what you he gan in Dav 2. The objective here is to further de what Wayne will need and how he will actually the system. You will determine exactly how each ue case works-what steps and options are availabe with the use case and even what the display and da entry screens will look like. These activities priman ily support Core Process 3: Discover and undersn details. Based on the scope and vision vou described in the System Vision Document, divide the project into at least two separate subsystems that can be done in sepa- rate iterations. For example, perhaps a first version can run on a laptop, with a second version that includes mobile components for a smartohone, These activities are related to Core Process 2: Plan and monitor the project-whar to do, how to do it, and who does it. Assignment D1-1: Divide the system into at least two separate components or subsystems, which can be supported with two iterations. Briefly de- scribe each. Assignment D3-1: Select a single use case and identify the steps required to perform the use case. (Hint: Think of what Wayne does and how the system responds. Assignment D1-2: Create a work breakdown structure that lists all the steps to complete the first iteration. Put a time estimate on each step. (Hint: Use the one in this chapter as a model. Assignment D3-2: Make a workflow diagram of the selected use case. [Hint: Drawing by hand is fine. Each step from D3-1 goes in an oval. Connect the ovals with arrows.] Day 2: Define and Understand the Requirements Assignment D3-3: Sketch out one of the screens that will be required to support a use case. The screen should allow for data entry and display of information. (Hint: Don't make it elaborate. Focus only on the input and output data fields that apply to only one use case. On Day 2, you want to get an overall view of what the system needs to do for Way ne. There are two pri- mary areas to focus on to obtain this high-level un- derstanding of the system: a list of use cases and a list CHAPTER 1From Beginning to End An Overview af Systens Analysis and Design 33 Day 4: Develop the Software Architecture Design The high-level software architectural design of the SYstem generally includes decisions about how the sys- rem will be built and what the databasse will look like. Design is a technical activity that requires experience in programming, database development, and software architecture. These activities support Core Process 4 Design system componets. you prefer. For this answer, draw on your previ- OUR programming and development experiences. THint: There are marny valid solutions. Give rea sons for your preference. Day 6: Test and Deploy the System You may have had opportunities to perform compre hensive testing of your programming class projects, especially if you have developed systems that inte- grated with other systems. These activities support Core Process 6: Complete system tests and deploy solution. Obviously, you can only do this if you have programmed the system. Assignment D4-1: Design a preliminary database schema for the classes in this iteration. [Hint: Each class becomes a table, The attributes be- come table columns. Assignment D6-1: Write a paragraph describing the difforence between programmer testing and user testing. (Hint: Why is it hard to test your own work? What do the users know that you don't know? Assignment D4-2: Decide whether you will build a desktop system or a browser-based system. Write a couple of paragraphs listing the pros and cons of each alternative to defend your decision. (Hint: Either option is valid. Think of reasons to support your decision.) Assignment D6-2: Write a paragraph describing all the issues that might need to be addressed to deploy this system, Hint: You might want to search the internet to learn about deployment issues.) Day 5: Develop the Detailed Design and Program the System You probably have had many class projects where you designed a system and then programmed it. These kinds of activities support Core Process 5: Build, test. and integrate system components. Assignment D6-3: Look at www.geocaching.com, which is a commercial Web site. What other issues need to be addressed to deploy this type of Web site? Hint: Think about all the issues related to se curity, robustness, financial protection, high vol- Assignment D5-1: Write a paragraph describing what programming languagels) you would rec- ommend and what development environment umes, uptime, different browsers, and so forth.]