Skip to main content

Analysis

Examining systems to understand how they work and how they should change.

Also Known As

Related

Addresses / Mitigates

  • Implementation Risk: Ensures that requirements and specifications are clearly understood before development begins.
  • Communication Risk: Facilitates clear communication of requirements and expectations among stakeholders.
  • Feature Fit Risk: Analysis can help ensure technical solutions fit the problems they're designed for.
  • Contextual Risk: Developing an understanding the context into which a solution is put avoids legal and social problems.

Attendant Risks

  • Schedule Risk: Can be time-consuming, potentially delaying the start of development.
  • Agency Risk: Creates dependencies on the availability and accuracy of information from stakeholders.
  • Boundary Risk: Well-defined analysis can create rigid boundaries that limit flexibility.

Used By

  • Lean Software Development: Lean uses value stream mapping to analyze the flow of materials and information, identifying areas of waste.

Description​

"Systems analysis is a problem-solving technique that decomposes a system into its component pieces for the purpose of studying how well those component parts work and interact to accomplish their purpose." - Systems analysis, Wikipedia

Analysis in software development involves examining and breaking down the requirements, systems, and processes to understand the needs and ensure the correct implementation of the software. This practice is crucial for identifying potential issues, clarifying requirements, and ensuring that the development aligns with business goals and user needs.

See:

See Also​

Lean Software Development

An Agile software development methodology that emphasizes eliminating waste, building quality in, creating knowledge, deferring commitment, delivering fast, respecting people, and optimizing the whole.