Summary:

For the efficient software development there is always need of a good software model to
be used. Spiral model is an iterative model which has covered lot of disadvantages of water fall
model. Twin peak model is derived from spiral model to use it in our own way. In this article the
author has talked about twin peak model and he says with his experience that requirements and
architecture should not be separate phases. He introduced a new model which focuses both
requirements and architecture simultaneously. It is derived from spiral model which is iterative
process means it can be change when we need to add a change in our requirements and
architecture. Twin peak model covers requirements and architecture at a time and make it easier
to build our logic and understand problem. Although this model develops requirements and
architectural specifications concurrently, it continues to separate problem structure and
specification from solution structure and specification, in an iterative process that produces
progressively more detailed requirements and design specifications. Twin peak model is a spiral
iterative model containing both requirements and architecture a same time.
Twin peak model explains three major management concerns identified by the author
Barry Boehm. First one is IKIWISI (Ill know it when I see it) which shows that a user will
understand the requirement and will give his feedback when he will be able to see it.
Architecture will help the user to understand his requirement when we will use twin peak model.
Twin peak model is iterative we can change requirements when user will understand the
requirements ask for change in requirements. Second one is COTS (Commercial off-the-shelf
software) increasingly, software development is actually a process of identifying and selecting
desirable requirements from existing commercially available software packages. With Twin
Peaks, developers can identify requirements and match architectures with commercially
available products, rapidly and incrementally. And third one is Rapid Change, Managing change
continues to be a fundamental problem in software development and project management. Twin
Peaks is receptive to changes as they occur. Addressing IKIWISI means starting design and
implementation earlier than usual, using COTS requires considering reuse at an earlier stage of
requirements specification.
The software design community has already identified design patterns for expressing a
range of implementations. The software architectures community has identified suitable

architectural styles for meeting various global requirements. We can treat patterns of
requirements, designs, and architectures as the starting point for component-based development.
Given that existing architectures can influence how developers structure problems, some
problem frames may need to be reverse engineered from existing architectural designs. Early
understanding of requirements and choice of architecture are key to managing large-scale
systems and projects. . Twin Peaks is inherently iterative, and combining it with tried and tested
components derived from well understood patterns can facilitate incremental development of
large-scale systems.

Design and Architecture:

What is Architecture?
Architecture is the set of major principles design decisions for the software development
process. In Architecture it is explained how system will be designed and implemented.
Architecture focuses on the development for whole system. Architecture is the overall view of
whole system.

What is Design?
The detailed explanation of different components and how they will be connected is
called design. Images, graphics and different types of diagrams are used in design which includes
use-case diagram, Dataflow diagram state transition model and UML etc. Design is the overall
view of components.

Difference between Architecture and design:

Architecture concerns about the whole system and its design principles and
Design focuses on the components as individually and also who they will be
connected to each other.