|
Quick Contact
|
Home
 Steps in Software DevelopmentSteps in Software Development A project always starts as an idea which generally provides a solution. Often these are drummed up in brainstorming sessions and scratched out onto legal pads or napkins. It is this step which leads to your project charter, or your declaration of dependence. The key in this phase is to include, from the start, all parties involved, including the most senior managers impacted by this effort. This means the technical team, development manager, project manager, business representatives from the impacted departments, and preferably, the CIO and a non-technical senior management representative. All software artifacts are represented generically within parameterized PVS theories which specify the semantic requirements on the parameters by means of assumptions and define the result of the transformation. Based on the semantic requirements, correctness of the generic step can be proved once and for all. Application of such a development step to a given problem is then carried out by providing a concrete instantiation for the parameters and verifying that it satisfies the theory requirements. Steps views software development in its connection to work design. It gives guidance to developers and users for carrying out their cooperation, establishing quality criteria pertaining to software in use and putting them into practice in system design. It embodies an evolutionary approach, portraying system development in cycles of version production, application and revision. It supports mutual learning by developers and users by carefully establishing and coordinating processes of cooperation, by using prototyping for experiments and by adapting methods and tools to the needs of cooperation and incremental work.Request For Quote Thank you for your interest in eDeveloper Network. Please kindly fill in our Request For Quote form and we will get back to you promptly regarding your request. |
