Analysis and Design
The most important step of the analysis and design stage is defining the system architecture. There are basically three different ways in which this stage might commence:
| Customer defined: | This is when the customer already has a clear vision and requires us to create the artefacts of the Requirements Gathering phase. In this situation, development work is underway immediately. | |
| iQuest defined: | In this case the customer provides the requirements artefacts and iQuest starts with the Analysis and Design process. | |
| Pre-defined: | This is where Analysis and Design are based on a pre-existing system and iQuest is asked to work within its parameters to make adjustments or integrate further applications or functionality (a new version, migration, maintenance etc). |
Generally we apply the Rational Unified Process (RUP), adapted to project specifics. Use-cases from the Requirements Gathering phase are mapped to design, during the use-case realisation stage.
Sometimes, however, a more informal approach is better suited, with daily interactions and highly iterative time-boxed implementation. This is where the agile approach is best adopted. The focus is on working-product versions, rather than documentation delivery.
Systems architect
iQuest systems architects are specialised in particular technologies, enabling them to recommend the best architectural components.
They also check the architecture against the non-functional requirements (load, security etc). They then deliver a proof of concept, at which stage applications are employed and architectural assumptions are checked.
Software architecture document
This key artefact encompasses:
- Definitions of key design mechanisms.
- Architecture outline - using multiple views (physical view, logical view).
- Interactions - between components and the system and external interfaces.
It’s important to us to always adapt to the customer and project needs. We’re more than happy to suggest the best approach to the problem at hand, but we can go beyond that, whenever required, offering a comprehensive solution to help drive your business goals.
Specific elements of our Analysis and Design approach include:
- GRASP Design mechanism (General Responsibility Assignment Software Patterns)
- Design Patterns (GOF)
- Patterns of Enterprise Application Architecture (Fowler)
- Responsibility Driven Design
The most important aspect and focus of all our design, however, is ensuring maintainability and scalability.
If it works for your business in the long run, it works for ours.