|
|
| Our Process |
|
| Development Process |
|
| Application Modelling |
|
|
Once the requirements are frozen, and the user interface is finalized, the next stage is to model the entire application. Unified Modeling Language T (UML®) is extensively used for modeling the application. UML helps you specify, visualize, and document models of software systems, including their structure and design. |
|
|
Any precise model must first define the key concepts of the application, their internal properties, and their relationship to each other. This set of constructs is the static view. The application concepts are modeled as classes. Each of these classes describes a set of discrete objects that hold information, and communicate to implement behavior. The information they have is modeled as attributes, while the behavior they perform is modeled as methods. Object to object relationships are modeled as associations among the classes. The static view is notated using the class diagram. The static view can be used to generate most data structure declarations in a program. (Source: The Unified Modeling Language Reference Manual) |
|
|
|
|
|
| |
 |
|
|
| |
The view of a system of interacting objects is collaboration. It is a context-dependant view of objects and their links to each other, together with the flow of messages between objects across data links. This viewpoint unifies data structure, control flow, and data flow in a single view. Collaborations and interactions are shown in sequence, and collaboration diagrams. |
|
| Data Modelling |
|
|
To capture fast paced complex businesses, we must consider methods that go beyond traditional ER diagrams. Maximize Technologies depends on Object Role Modeling (ORM) for its data modeling. ORM is a method for designing and querying database models at the conceptual level. Here the application is described in terms readily understood by users, rather than being recast in terms of implementation data structures. The architect develops an information model by interacting with others who are familiar with the application. Because these subject matter experts need not have technical modeling skills, reliable communication occurs by discussing the application at a conceptual level, using natural language, analyzing the information in simple units, and working with instances (sample populations). Like any good modeling method, ORM is far more than a mere notation. It includes various design procedures to develop and evolve conceptual models. |
|
| |
Once all the facts are expressed and an ORM model is created, tables can be generated automatically. The design of the database is automatically normalized to the fifth normal form. All relationships, constraints, and default values are maintained when the database is created. |
|
| |
 |
|
| Creating the Quality and Deployment Document |
|
|
During the course of architecting the software, the architect creates the test plans and quality documents. These documents help the Quality Assurance team to test the product thoroughly, and ensure the quality of the product. The architect also generates a deployment plan for the deployment team. The architect uses the deployment diagrams to explain the deployment of the application. |
|
| |
|
|
|
|
|
|
|
