System Analysis & Design Chapter 2

A methodology where a prototype system is built and used by users, allowing interactions and feedback to refine requirements.

Prototyping provides early user interaction, reassures users, helps refine requirements faster, and allows users to better understand the system's capabilities/limitations, quickly identifying issues.

Rapid prototyping can lead to changes so significant in the design process that initial decisions become problematic, particularly in complex systems.

A prototyping approach where prototypes are developed for a specific purpose, used for analysis and refinement, to identify and resolve issues, not for actual implementation.

Throwaway prototypes are used to explore challenging technical issues or ensure users understand complex features, not for full system implementation.

A non-functional representation of a system's component used in throwaway prototyping for user understanding in specific areas with essential details, not the whole system.

In throwaway prototyping, a detailed analysis phase precedes the development of prototypes, focusing on gathering requirements from users.

A systems development methodology that uses prototypes to identify and resolve issues before building the final system. The prototypes are discarded after use.

A preliminary version of a system used to evaluate potential design solutions during analysis and design.

An iterative and flexible software development approach emphasizing collaboration, flexibility, and continuous improvement.

Simplified visual representations of parts of a system, often used for user visualization during the analysis phase. They do not function as a real system.

Formal procedures to create quality software systems.

A software development methodology focusing on rapid prototyping, iterative development, and user involvement, usually delivering quicker results compared to other methods like throwaway prototyping.

A software design method focused on building systems using modular approaches with clear hierarchical diagrams to model the system.

XP involves testing code frequently throughout the development process, aiming for a bug-free integrated code base.

Two programmers work together on the same computer to build code, fostering collaboration and knowledge sharing.

A disciplined approach to restructuring code without changing its external behavior; making the systems clean.

Short descriptions of what a system needs to do from the user's perspective, used to structure XP projects.

XP projects develop software in short cycles (iterations) with daily stand-up meetings, pair programming and testing focused on delivery of features or small systems.

XP emphasizes creating small, comprehensible code units using pair programming to promote manageable and maintainable outputs.

Successful XP projects typically involve highly motivated, cohesive, stable, and experienced teams working on small projects.

XP projects focus primarily on code documentation and rely on minimal analysis or design documents.

A software development approach focused on flexibility, collaboration, and responding to change.

Agile prioritizes working closely with customers throughout the development process rather than just formal contracts.

Agile values the skills and communication of the development team over rigid processes or tools.

Agile emphasizes delivering functional software frequently over extensive documentation.

Agile prioritizes adapting to changes, even late in the project, over sticking to a rigid plan.

Short, time-boxed iterations in agile projects that deliver functional software.

Regular, short meetings in agile, where team members update each other on progress, roadblocks, and plans.

An agile software development methodology emphasizing communication, simplicity, feedback, and courage.

Rapid feedback and constant communication with the user in extreme programming

Keep things simple and use the KISS approach for development in extreme programming

Getting user feedback constantly and promptly in extreme programming

Embracing change and following through on improvement plans in extreme programming

A group of software development approaches that include Scrum and Kanban.

Selecting the best approach for building a system, considering factors like user needs, tech familiarity, system complexity, time constraints, and visibility.

Understanding what users need from a system, focusing on interactions and how they use the system.

Assessing developers' knowledge of the technologies used in a system.

The level of detail and intricacy in a system's design.

Time constraints in software development.

The extent to which the development schedule is clearly defined and trackable.

Approaches emphasizing early user interaction and feedback before building a final system.

Prototypes created for analysis, refinement, and issue resolution, not final implementation.

A system design approach that focuses on detailed analysis before implementation, using modular/hierarchical structures.

Developing a system in stages, investigating technology and refining designs step-by-step.

A systems development approach where the system is built in stages, allowing users to interact early in the process.

The extent to which a methodology supports deep analysis of all the problems that must be addressed.

The dependability of a system to work correctly and consistently.

A prototyping methodology where prototypes are developed purely to understand the system, discard to improve the original design.

Prototyping might not be ideal when reliability matters; thorough designs are preferred

Rapid Application Development (RAD) methodologies are good for projects with tight deadlines.

Waterfall methodologies are not suitable for projects with tight deadlines due to lack of flexibility.

Determining if a project is on track, a common challenge in systems development

Structured design methodologies might have issues with schedule visibility as design and implementation occur later.

RAD methodologies bring important design decisions earlier to help project managers see risks and manage expectations

Formal approaches to creating high-quality systems