Typical development phases of a project

Software Development Lifecycle/Process

A software development lifecycle/process is a structure imposed on the development of a software product. There are several methodologies/models which DAJ may use to include the follow:

Process Improvement model

For such processes, each describes approaches to a variety of tasks or activities that take place during the process, for example the Waterfall Model below.



DAJ uses the methodology most appropriate for the project, hence, the waterfall model could be used where the tasks are executed in linear sequence and the Rational Unified Process (RUP) works better for larger projects of undefined and ambiguous nature. As for problem solving, DAJ typically follows the common steps to — "defining the problem, weighing options, choosing a path, implementation and evaluating the end product."

Requirements Analysis

Requirements analysis in the systems engineering and software engineering process encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders such as beneficiaries, subject matter experts or users.
Requirements analysis is critical to the success of a development project. Requirements must be actionable, measurable, unambiguous, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design. Requirements can be functional and non-functional and follow a similar process as below.



Some projects do not follow structured planning and/or monitoring stages. Some projects will go through the “Planning and Designing”, “Executing”, and “Monitoring and Controlling” phases multiple times.

Content Management

DAJ has effectively supported a number of Content Management Systems (CMS) to include ECM Documentum, MS Sharepoint and IBM FileNet. 

A CMS is a collection of procedures used to manage work flow in a collaborative environment. These procedures can be manual or computer-based. The procedures are designed to:

In a CMS, data can be defined as nearly anything - documents, movies, pictures, phone numbers, scientific data, etc. CMSs are frequently used for storing, controlling, revising semantically enriching, and publishing documentation. Content that is controlled is industry-specific. For example, pharmaceutical content differs from the design documents for transportation. There are various terms for systems (related processes) that do this. Examples are web content management, digital asset management, digital records management and electronic content management. Synchronization of intermediate steps, and collation into a final product are common goals of each.

User Acceptance Testing

User Acceptance Testing (UAT) is a process to obtain confirmation by a Subject Matter Expert (SME), preferably the owner or client of the object under test, through trial or review, that a system meets mutually agreed-upon requirements. In software development, UAT is one of the final stages of a project and often occurs before our client accepts the new system.

DAJ’s test designers draw up formal tests and devise a range of severity levels. Users of the system perform these tests, which are developed and presented via test scripts. The UAT acts as a final verification of the required business function and proper functioning of the system, emulating real-world usage conditions.
The results of these tests give confidence to our clients as to how the system will perform in production while satisfying the contractual requirements for acceptance of the system.

IT Training

When the system has been deployed, tested and accepted by our clients, if tasked, DAJ would strategically coordinate the system training which may include the following: 

Classroom Training
Net meeting / web meeting
Train-the-Trainer
Produce User Manuals
Produce System Manuals
Produce Administrator Manuals