Software Engineering and Architecture

Waterfall system:

Requirements -> Design -> Implementation -> Verification -> Maintenance

Also a traditional methodoligy in Softare engineering.

Principles:

• Iterative and incemental
• Use case driven
• Architecture centric
• Risk focused

Issues:

• Can be "process" and "artifacts" heavy
• Is there a "transition" phase?

• Project Failure is too high
• Despite the application of (heavyweight) methodologies, technology projects still regularly fail more than would be acceptable in any other industry
• The evolution of technology (hardware) and tools (IDEs etc.) has outstropped methodologies by an oder of magnitude

• 57%: Poorly scoped projects
• 44% Technical or integration issues
• 36%: Poor implementation staff or services
• 35%: Buggy software
• 30%: Unattainable business requirements
• 27%: Loss of executive sponsorhips

For reasons 1, 3, 5 & 6  the methodology didn't work. For the others was the solution the problem.

• Methodologies to make software development process more disciplied and predictive
  • More planning
  • Greater Attention on analysis of reqirements (-> Reqirements Engineering)
  • Tie down scope and sign-off
  • Detailed and documented design before coding
  • Strict change control to suppress change

Set of values and principles shared by representatives from 

• Extreme Programming, SCRUM, DSDM,
• Adaptive software development, Crystal
• Feature-Driven development, Pragmatic Programming
• and others sympathetic to the need for an alternative to documentation driven, heavyweight software development process

founded it 2001.

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

• The highest priority is to satisfy the customer through early and continuous delivery of valuable software
• Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
• Deliveer working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
• Business people and developers must work together daily throughout the project.
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the ob done.
• The moste efficient and effective method of conveying infromation to and within a development team is face-toface conversation.
• Woring software is the primary measure of progress
• Agile processes promote sustainable develpment. The sponsors, develepers, and users should be able to maintain a constant pace indefinitely.
• Continzous attention to technical excellence and good design enhances agility.
• Simplicity- the art of macimizing the amount of work not done - is essential
• The best architectures, requirements, and designg emerge from self-organizing tems.
• At regular intervals, the team revlects on how to become more effective, then tunes and adjusts its behavior accordingliy.