At AERON Software we follow a process oriented development methodology designed to minimize project risks and development time. We focus on business solutions that fulfill business goals, instead of merely providing technical solutions. All our applications are built on the basis of this philosophy.
Every project in AERON goes through one or more phases of Software Development Life Cycle (SDLC). Typically, a SDLC has following phases – Requirement Definition, Analysis, Design, Implementation/Development, Integration &Testing, Deployment and Acceptance. Depending on the project requirements, the technology environment - some of the SDLC phases may be modified. Here at AERON, we use various SDLC models like Waterfall, Spiral, Rapid prototyping model etc. .
Requirement Definition In this stage, the requirements of the clients are gathered. This is done on the basis of information provided by the client in the form of documents, existing systems & process specs, on-site analysis interviews with end-users, market research and competitor analysis.It is important to gather the non-functional requirements which generally describe the application performance because these requirements may impact the architecture and design. This stage has the following steps:
- Requirements analysis with business application goal and high level requirement gathering
- Creation of visual scope document and feature list
- Providing technical recommendations and high level requirement specification
Analysis In this stage, a detailed analysis is carried out from the information in the vision & scope document and feature list. This stage has the following steps:
- Analysis and creation of Software Requirement Specification
- Creation of Use Case Specification & Diagram and generating the Use Case Model
- Design business rules and flow diagrams
- Establishment of Requirement Traceability Matrix
- Validation of the Scope and Estimates against the contract and revisions made if necessary
Design In this stage, the application design is developed on the basis of the Software Requirement Specifications, Use Case Specification, Business Rules & Diagrams and the scope agreed upon in the Requirement Definition stage. This stage has the following steps:
- Designing Architectural Diagrams
- Creation of High Level Design and Low Level Design class diagrams
- Establishment of Entity Relationship Diagram, Data Flow Diagram and Deployment Diagrams
- User Interface - The prototype is developed and validated against the requirement and presented to the client for approval
- The use cases elaborated in the analysis model are represented using collaboration diagrams
- Design model elaborations are made from the analysis model. Validation of the scope, estimates against the contract and revisions are made if necessary
- The Implementation Model is generated from design
- The Test Model is generated from use cases
Development In this stage, the actual code based on the design is created and tested against design requirements and test cases. This stage has the following steps:
- The development of code base proceeds as per implementation and design models
- The application source code is tested according to the test cases and test plan
- Documentation of processes
- Creation of Use Case Test results
Integration and Testing
- In this stage, the developed application is tested through test cases, test plans and user acceptance criteria in the deployed environment.
- Integration and quality testing is carried out resulting in test reports.
- Client acceptance tests carried out.
- Client feedback and debugging.
- Client acceptance
Deployment and Acceptance
- In this stage, the developed application is deployed on the live server.
- Integrated application and deployment plan
- Implementation on client premises or hosting server.
- Implementation signoff by client.
- Creation of archived software
- Transition of application to the maintenance team.
The steps above are iterated through until the final deliverable is completed.