Process management
Process management is the discipline of defining and achieving targets while optimizing the use of resources (time, money, people, space, etc). Thus classified into several models: time, cost, scope, and intangibles. Without project management, software projects can easily be delivered late or over budget.

Process steps
Maasys InfoTech follows the following procedure.

Requirements Analysis
Extracting the requirements of a software product is the first task in creating it. While customers probably believe they know what the software is to do, it may require skill and experience in software engineering to recognize incomplete, ambiguous or contradictory requirements.

Planning
Required to determine the feasibility of whether the project should proceed or not.
Produces a high level overview document of the project which relates to the project requirements and scope.
To include requirements for data replication to the warehouse.

Defination
Defines what, when, who, and how the project will be carried out.
This phase expands on the high-level project outline and provides a specific and detailed project definition.
This phase assumes that an RFP has been prepared and distributed, a contract project development team chosen and a Project Manager appointed.

Analysis
Required to understand and document the user's needs for the system.
Documents in detail the scope, business objectives and requirements of the system.
Emphasizes what the system is to do.
Includes analysis of what data needs to be replicated to the data warehouse.

Design
Describes how the proposed system is to be built.
The design is specific to the technical requirements the system will be required to operate in and the tools used in building the system.
Impacts the build and implementation phases of the SDLC.
Describes movement of data between operational databases and the data warehouse.

Build
Deals with the development, unit testing and integration testing of the system modules, screens and reports and data replication to the data warehouse if required.
Carried out in parallel with the development of user procedures and user documentation from the implementation phase.

Testing & Implimentation
Prepare for and carry out the testing of the developed system. And user acceptance testing to full production and warehouse population and implementation.

Documentation
An important (and often overlooked) task is documenting the internal design of software for the purpose of future maintenance and enhancement. Documentation is most important for external interfaces.

Maintenance
Maintaining and enhancing software to cope with newly discovered problems or new requirements can take far more time than the initial development of the software. Not only may it be necessary to add code that does not fit the original design but just determining how software works at some point after it is completed may require significant effort by a software engineer. About 2/3 of all software engineering work is maintenance, but this statistic can be misleading. A small part of that is fixing bugs. Most maintenance is extending systems to do new things, which in many ways can be considered new work. Similarly, about 2/3 of all civil engineering, architecture, and construction work is maintenance in a similar way.