1 / 18

Determining System Requirements

Determining System Requirements. Week 4 CMIS570. SDLC. Project Planning. Analysis. Design. Implementation. Support. Requirements Determination. System requirements Functional requirements Current and future functions Current and future data Current and future employee jobs.

ringo
Download Presentation

Determining System Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Determining SystemRequirements Week 4 CMIS570

  2. SDLC Project Planning Analysis Design Implementation Support

  3. Requirements Determination • System requirements • Functional requirements • Current and future functions • Current and future data • Current and future employee jobs

  4. Other requirements to consider • Technical requirements • Performance requirements • Usability requirements • Reliability requirements • Security requirements

  5. Requirements Structuring • Three essential views of the current and replacement information systems • Process view: The sequence of data movement & handling operations within the system • Data flow diagrams • Logic and timing: Rules by which data are transformed & manipulated & an indication of what triggers data transformation • Structured English, Decision tables, Decision trees, State-transition diagrams • Data: The inherent structure of data independent of how or when it is processed • Entity-relation diagrams

  6. Remember to... Assume Anything is Possible Question Everything Pay Attention to Details Don't Jump to Conclusions Be Impartial

  7. Who will you get info from? • User Stakeholders • Users • Managers • Client Stakeholders • Technical Stakeholders

  8. What Information Do You Need? • 1. • 2. • 3.

  9. Techniques for Determining System Requirements • Review existing documentation • Observation • Interviews • Building a prototype • Questionnaire • JAD

  10. Existing documentation/observation • Work procedures describe a particular job or task • May show duplication of effort • May find missing steps • May contradict info collected from interviews, questionnaires, and observations • Formal systems vs informal systems

  11. Strengths Doesn’t rely on a user’s memory More objective and accurate than interviews Weaknesses Hawthorne effect Time consuming Directly observing users

  12. Conducting interviews

  13. Other things to remember • Use both open-ended and close-ended questions • Take advantage of follow-up questions, visual cues • Interview in groups

  14. Strengths 1. 2. 3. Weaknesses 1. 2. 3. Distribute and collect Questionnaires

  15. Give Me Ambiguity or Give Me Something Else! • How often do you back up your computer files? • A. Frequently • B. Sometimes • C. Hardly at all • D. Never

  16. This is better… • How often do you back up the computer files stored on the hard disk on the PC you use for over 50% of your work time? • A. Frequently (at least once per week) • B. Sometimes (from 1 to 3 times per month) • C. Hardly at all (once per month or less) • D. Never

  17. Modern Methods for Determining System Requirements • Prototyping • Joint Application Design (JAD) - Intensive meetings between users, managers, sponsor, & systems analysts to discuss & review system requirements • Group Support Systems (GSS) to share ideas & voice opinions • Vendor solutions • CASE tools to analyze existing systems

  18. Structured Walkthroughs • What is it? • When is it done? • Who is involved? • How is it done?

More Related