Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
CIS454-Ch.1(Part 2)
Introduction to Systems Analysis and Design
| Term | Definition |
|---|---|
| Methodology | A formalized approach to implementing the SDLC (i.e. - it is a list of steps and deliverables). |
| Process-Centered Methodology | Emphasizes process models as the core of the system concept. |
| Data-Centered Methodologies | Emphasizes data models as the core of the system concept. |
| Object-Oriented Methodologies | Attempt to balance the focus between process and data by incorporating both into one model. |
| True | Another important factor in categorizing methodologies is the sequencing of the SDLC phases and the amount of time and effort devoted to each. |
| 3 Different Classes of System Development Methodologies | 1) Structured design 2) Rapid Application development 3) Agile Development |
| Structured Design | Methodology which adopts a formal step-by-step approach to the SDLC that moves logically from one phase to the next. |
| 2 Structured design categories | 1) Waterfall development 2) Parallel development |
| Waterfall Development | Analysts and users proceed in sequence from one phase to the next; key deliverables are long and presented to the project sponsor for approval as the project moves from phase to phase. |
| Structured Design | __________ ______ introduced the use of formal modeling or diagramming techniques to describe the basic business processes and data that support them. |
| 2 Advantages of Structured Design Waterfall Approach | 1) Identifies system requirements long before programming begins 2) Minimizes changes to the requirements as the project proceeds |
| 2 Disadvantages of Structured Design Waterfall Approach | 1) Design must be completely specified before programming begins 2) A long time elapses between the completion of the system proposal in the analysis phase and the delivery of the system. |
| True | A system can require significant rework because the business environment has changed from the time that the analysis phase occurred. |
| Parallel Development Methodology | addresses the problem of long delays between the analysis phase & delivery of the system; performs a general design for the whole system & divides entire project into a series of distinct sub-projects that can be designed & implemented in parallel. |
| Parallel Development | The primary advantage of ________ ___________ methodology is that it can reduce the time to deliver a system, creating less of a chance of changes in the business environment causing rework. |
| Rapid Application Development (RAD) | Methodology category which adjusts the SDLC phases to get some part of the system developed quickly and into the hands of the users, so they can better understand the system and suggest revisions that bring the system closer to what is needed. |
| RAD | The main problem with ___-based methodologies is managing user expectations. |
| Phased Development-based Methodology | Breaks an overall system down into a series of versions that are developed sequentially. |
| Phased Development | ______ ___________-based methodologies have the advantage of quickly getting a useful system into the hands of the users. |
| Prototyping-Based Methodology | Performs the analysis, design, and implementation phases concurrently, and all three phases are performed repeatedly in a cycle until the system is completed. |
| System Prototype | A quick-and-dirty program that provides a minimal amount of features. |
| Prototyping | The key advantage of a ___________-based methodology is that it very quickly provides a system with which the users can interact. |
| Prototyping | The major problem with _________ is that its fast-paced system releases challenging attempts to conduct careful, Methodical analysis. |
| Throwaway Prototyping-based Methodologies | Includes the development of prototypes; have a relatively thorough analysis phase that is used to gather information and to develop ideas for the system concept. |
| Design Prototype | Is not an actual working system; it is a product that represents a part of the system that needs additional refinement & it contains only enough detail to enable users to understand the issues under consideration (i.e. - mock-up). |
| Throwaway prototyping | _________ ___________-based methodologies balance the benefits of well-thought-out analysis & design phases with the advantages of using prototypes to refine key issues before a system is built. |
| Agile Development | Based on a manifesto and 12 steps; the emphasis of the manifesto is to focus the developers on the working conditions of the developers, the working software, the customers, and addressing changing requirements; it is very programming-centric. |
| 12 Principles of Agile Software | 1)Delivered early2)Change embraced3)delivered frequently4)Customers&developers work together5)Motivated individuals create solutions6)F2F comm.7)Measure=working software8)Sustainable work pace9)Agility10)Simplicity 11)Self org. teams12)Team reflection |
| Agile Methodologies | _____ _____________ focus on streamlining the system-development process by eliminating much of the modeling and documentation overhead and the time spent on those tasks. |
| Extreme Programming (XP) | Funded on 4-core values: 1) Communication 2) Simplicity 3) Feedback 4) Courage Testing & efficient coding practices are as the core. |
| XP | __ is recommended for only small groups of developers - no more than 10 developers - and it is not advised for large mission-critical applications. |
| SCRUM | Uses sprints which last 30-working days. At the end of each sprint, a system is delivered to the customer; comprises the most chaotic, change-centric systems development approach. Teams have no leader and are self-organized. |
| True | A typical SCRUM team size is 7 members. |
| RAD & Agile | ___ & _____ methodologies are usually more appropriate when user requirements are unclear. |
| True | If a system is designed without familiarity with the base technology, risks increase because the tools might not be capable of doing what is needed. |
| Object-Oriented | ______-________ approaches are most associated with a phased development RAD or agile methodology. |
| Object-Oriented Methodologies | Methodologies that use the RAD-based sequence of SDLC phases but attempt to balance the emphasis between process and data by focusing the decomposition of problems on objects that contain both data and processes. |
| True | Any modern object-oriented approach to developing information systems must be use-case driven, architecture-centric and iterative and incremental. |
| Use-case Driven | Means that use cases are the primary modeling tools defining the behavior of the system. |
| Use Case | Describes how the user interacts with the system to perform some activity, such as placing an order, making a reservation, or searching for information. |
| Use Case | A ___ ____ focuses on only one business process at a time, so developing models is much simpler. |
| Architecture Centric | Means that the underlying software architecture of the evolving system specification drives the specification, construction, and documentation of the system. |
| 3 Object-Oriented Views of a System | 1) Functional 2) Static 3) Dynamic |
| Functional (External) | View which describes the behavior of the system from the perspective of the user. |
| Structural (Static) | View which describes the system in terms of attributes, methods, classes and relationships. |
| Behavioral (Dynamic) | View which describes the behavior of the system in terms of messages passed among objects and state changes within an object. |
| Iterative & Incremental | Development that undergoes continuous testing and refinement throughout the life of the project. |
| True | Concepts in the object-oriented approach enable analysts to break a complex system into smaller, more-manageable modules, work on the modules individually, and easily piece the modules back together to form an information system. |
Created by:
Jordan.WBL