The Model Driven Development Paradigm

The first milestone will be concept approval. During this phase, feasibility studies and basic system concepts have been approved by the management. The project is on course to proceed according to the detailed requirements. The next milestone is requirements review. During this stage, requirement specifications are ready, correct, and approved for input to the design. The next milestone will be preliminary design review here the architectural design meets all product requirements. Critical design review will then follow. During this phase, the detailed designs are approved and suitable for the development of test cases. The next milestone will be the test plan review, which involves reviewing the test plan to ensure product features are satisfactory. The next milestones will be tested readiness review, system test review, operational readiness review, and operational product

Another way of successfully gathering information is by building a prototype or model of the system, so that users can test or get an idea of what the finished product will be like. With this they can determine issues, problems, or inconsistency with the system. Another important part of gathering information is organizing it so that it can be understood and put to proper use. I propose categorizing the requirements into functional requirements, operational requirements, technical requirements, and transitional requirements. The functional requirements define how the user thinks the system is functioning overall, the operational requirements define what background processes need to be executed in order for the system to work optimally over a period of time, the technical requirements define what technical issues that must be addressed in order to successfully implement the system, and the transitional requirements define the processes or steps needed to implement the system smoothly and successfully. ("Mind Tools", 2012).

Software Engineering is the discipline of designing and developing software projects so that they behave in an efficient and independent manner while meeting the requirement of the client. Some key problems which arise in software engineering are complexity, inefficient communication and inadequate testing. Software projects are large and take years to make. In order to reduce the risk of failure and keep track of problems, software projects must follow the correct methodology.

Which is requirements needed, after all the information the team will analyze to determine software requirements and generate a report. Then we move to the selection and design, this will occur when the team creates several designs and share with everyone on the project. We will identify any weakness, if we have any successful prototypes it should show how the software will operate. Implementation phase should proceed without any issues if there is any it must be correct during this time. A planned out schedule should allow for any unexpected incidents. When the implementation stage is complete we move to operation when our software has been designed and does what it was designed to do. We will do a review and evaluation which consist of performance, cost and

The information system’s requirements in the systems planning phase are based on a case summary, potential interview questions, and the systems analyst’s experience in systems planning. One must not only generate requirements based specifically on what users’ state they want or need. Analysts must also generate requirements based on insight into the overall organization and project goals.

After full implementation, the system will enter the maintenance phase. Depending on the term of the contract, Smith will be involved in the maintenance phase of the system through its live cycle. All contracts include phone support for as-designed elements of the system.

This research paper will be focus on different software modeling techniques. Software modeling is concerned with development process of software. Software modeling is central part of almost all activities that took place in software development. These models help us to envision a system according to our requirement by describing the structure and behavior of the system. There are three basic techniques of software modeling; object oriented modeling, dynamic modeling and functional modeling. Object oriented modeling concept start in 1990s, its basic building block is object that is the instant of any class, and here class is a template containing attributes and methods of objects. Classes and their relationships are present in class diagram. As a class have many type of relations with other class within a class diagram. These relationships are about inheritance and some are about

Requirement elicitation and analysis was done in series of steps. Firstly, we carefully read and analyzed the product description to identify project context. After this stakeholders of the system and the roles of these stakeholders were identified. Raw requirement for the system were identified on the basis of the

➢ Studies and documents the current system – in terms of its problems, requirements and processes.

Marketing- This is the first among the 7 Phases of a Design Specification. Marketing is defined as a societal process, therefore in essence, it involves the interaction between the designers/manufacturers and the clients/customers. For a product/service to be well received by the target market, the designers should gather information relating to the wants and needs of the consumers. This can be in a form of a survey to determine the type of product/service that is most appealing to the consumer.

After the proposed system is analyzed and designed, the actual implementation of the system occurs. After implementation, working system is available and it requires timely maintenance.

The Waterfall Model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the

Model-driven improvement (MDD) is a software designing approach that uses model to make software. Model-driven advancement is now and then utilized reciprocally with model-driven engineering, and may allude to particular tools and resources, or a model-driven methodology. A model is a simplified representation used to explain the workings of a real world system or event.

In system analysis phase, an analysis is done on the current system functionality and also evaluation of the requirements from the users for the new system is done.

As a result of these weaknesses of the waterfall model, the spiral model was developed which emphasizes iterations of the phases with each phase producing on early Prototype representing a part of the overall system. This helps in demonstrating a proof of concept early in development. This model is similar to the incremental model, but with more emphasis placed on risk analysis. A software project repeatedly passes through these phases in iterations (called spirals in this model). The baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each subsequent spirals builds on the baseline spiral.