Test 2 - Requirements Modeling, Chapter 4 Identify systems...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Requirements Modeling, Chapter 4 Identify systems analysis phase activities and the end product of the systems analysis phase Requirements modeling – fact finding to describe the current system and identification of the requirements for the new system, such as outputs, inputs, processes, performance and security Data and process modeling – graphically represent system data and processes by identifying data flows and business rules that transform the data Object modeling – combines data and processes into objects that represent actual people, things, transactions or events Development strategies – deliverable, end product = system requirements document that provides overall design for the new system Explain joint application development (JAD), rapid application development (RAD), and agile methods JAD – user oriented technique for fact finding and requirements modeling, used when group input is desired o Most expense and cumbersome if the group is too large o Allows key users to participate effectively, stronger commitment to success o More accurate statement of system requirements and better understanding of goals RAD – condensed version of the SDLC, users involved every step of the way, fast track approach to a full spectrum of system development tasks o End product is the new information system o Reduces cost and development time o Successful team needs IT resources, skills and management support o Stresses mechanics of the system itself Agile – stressed intense interaction between system developers and users o Developers continuously revise, extend and merge earlier versions into final o Very flexible and efficient when dealing with change o Scrum sessions – emphasize time blocks, interaction, team based activities o Subject to significant change in scope Explain how systems analysts use a functional decomposition diagram (FDD) FDD (structure charts)– top down representation of a function or process, analyst can show business function and break them down into LL functions and processes, used during requirements modeling Describe the Unified Modeling Language (UML) and explain use case diagrams and sequence diagrams
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
UML – method of visualizing and documenting software systems design, uses o-o concepts but is independent of specific programming languages and can be used to describe processes generally Use case diagram – represents the interaction between users and the information system, user becomes an actor Sequence diagram – shows the timing of interactions between objects as they occur, used by analysts to show all possible outcomes or focus on a single scenario, process from top to bottom along vertical timeline Identify and describe system requirements, including outputs, inputs, processes, performance, and controls 1. Outputs – must report volume statistics, produce daily report, provide sales tracking 2. Inputs – swipe ID cards, student grades through scantrons, data entry screen are uniform
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 6

Test 2 - Requirements Modeling, Chapter 4 Identify systems...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online