MILESTONE 3 – MODELING SYSTEM REQUIREMENTSSynopsisObjectivesPrerequisitesAssignmentActivitiesPlease email these deliverables to the TA and the instructorReferences:Milestone 2 SolutionTranscripts of InterviewTemplatesDeliverables:Use-Case Glossary: Due: __/__/__ Time:_______Use-Case Model Diagram: Due: __/__/__ Time:_______Fully-documented Use Case Narrative: Due: __/__/__ Time:_______ADVANCED OPTIONFor the advanced option, prepare fully-documented Use-Case Narratives for additional use cases as directed by your instructor.Fully-documented Use Case Narratives: Due: __/__/__ Time:_______Milestone’s Point Value: _______SADM 7/ed – ESSS CASE STUDY - Milestone 3: Modeling System Requirements Page 3-1 ESSSMILESTONE 3 – MODELING SYSTEM REQUIREMENTS Synopsishe requirements analysis phase answers the question, ‘What does the user need and want from the new system?’ The requirements analysis phase is critical to the success of any new information system! In this milestone we need to identify what information systems requirements need to be defined from the system users’ perspectives. TUse-case modeling has gained popularity as a technique for expressing system requirements for two reasons: (1) it facilitates user-centered development, which often leads to building systems that better satisfy user needs, and (2) use cases diagrams and narratives are easy for users to understand.In this milestone you will first uncover the actors, use cases, and relationships that define the requirements for the proposed system and document that information in a Use-Case Glossary. You will use that to build a Use-Case Model Diagram for the system and a Use-Case Narrative for one use case. ObjectivesAfter completing this milestone, you should be able to: Understand and perform the techniques for requirements discovery. Determine actors, use cases, and relationships. Construct a Use-Case Glossary. Construct a Use-Case Model Diagram. Write a fully-documented Use-Case Narrative. PrerequisitesBefore starting this milestone the following topics should be covered:1. Requirements discovery – Chapter 6Prepared by Gary B. Randolph forSystems Analysis & Design Methods 7edby J. L. Whitten, L. D. Bentley, & K. C. Dittman Copyright Irwin/McGraw-Hill 2007SADM 7/ed – ESSS CASE STUDY - Milestone 3: Modeling System Requirements Page 3-22. Use-case modeling – Chapter 73. Milestone 2 Solution AssignmentNow that we have studied the current system and analyzed some of its problems and opportunities, plus gained approval to proceed, we can now start to identify the business requirements for the system and model them. In this assignment we will use our results of the previous milestones and transcripts of an interview with president Peter Charles, IT consultant Jeff Summers, and web server administrator Dane Wagner of Coastline Systems Consulting. The results of this activity will identify the system requirements for the proposed system.Exhibit 3.1 is a copy of the transcript of the interview. Refer to the transcript, sample forms, and results from Milestones 1 and 2 for the information necessary to complete the activities. Activities1. Complete a Use-Case Glossary. Make assumptions where necessary. 2. Prepare a Use-Case Model Diagram. 3. Prepare a fully-documented Use-Case Narrative for the Search Employee Directory use case described in the interview.Please email these deliverables to the TA and the instructorReferences:Milestone 2 SolutionProvided by your instructorTranscripts of Interview Exhibit 3.1TemplatesSee on-line learning center website for the textbook.Deliverables:Use-Case Glossary: Due: __/__/__Time:_______Use-Case Model Diagram: Due: __/__/__Time:_______Fully-documented Use Case Narrative: Due: __/__/__Time:_______Prepared by Gary B. Randolph forSystems Analysis & Design Methods 7edby J. L. Whitten, L. D. Bentley, & K. C. Dittman Copyright Irwin/McGraw-Hill 2007SADM 7/ed – ESSS CASE STUDY - Milestone 3: Modeling System Requirements Page 3-3ADVANCED OPTIONFor the advanced option, prepare fully-documented Use-Case Narratives for additional use cases as directed by your instructor.Fully-documented Use Case Narratives: Due: __/__/__Time:_______Milestone’s Point Value: _______Prepared by Gary B. Randolph forSystems Analysis & Design Methods 7edby J. L. Whitten, L. D. Bentley, & K. C. Dittman Copyright Irwin/McGraw-Hill 2007SADM 7/ed – ESSS CASE STUDY - Milestone 3: Modeling System Requirements Page 3-4The following is a copy of the transcript of an interview between Dotty Jones, Manager of Employee Relations, and Kira Webster, who is serving as systems analyst for the project. Dotty is the key user contact for this project. The goal of this interview was to determine requirements for the proposed system.Exhibit 3.1Scene: Kira Webster, computer information systems student, is meeting with Dotty Jones, Manager of Employee Relations, at Ms Jones' office.Kira: Good morning, Ms. Jones.Dotty: Hi. How can I help you today?Kira: The next step is to prepare what are called use cases. These detail out the interaction between users and the system to accomplish user goals. They help us document the requirements for the system so that we build what you really need.Dotty: Well, I'm all for that. How do we proceed?Kira: What I want to get out of this meeting is an understanding on everything the Employee Self Service System needs to do and who will be using each part of that functionality. Why don't we talk about the employee directory part of the system first? As I understandit, any employee can view the phone numbers for any other employee. Would they just get the whole list, or would it be searchable somehow?Dotty: First, it would be more than just phone numbers. It would have the employee's office location, department, job title, and supervisor. I think it should be driven by some sort ofsearch screen. In my experience, one might want to search by first or last name, department, location, job title, or supervisor. Or combinations of them. Can we do that?Kira: Sure. We can give the user a screen to enter any or all of that. When the user clicks OK, the system would first show the user a list of everyone who matches that criteria and links on each person to go view the complete information. Does that sound good?Dotty: Absolutely. But only after they do a successful logon. This is confidential information that can't be open to the public.Kira: Right. Now, we have to think
View Full Document
Unlocking...