Almost all top most companies engaged in the field of software development follow best practices followed in the field of software engineering.The solution provided by McDaav Systems is based upon the Rational Unified Process and we follow UML 2.0 specification while doing System Analysis.

Mcdaav Systems follows IEEE standards while designing the system. We deliver the project with full documentation which helps our client in understanding all the details of the Softwares.

Project Flow -

System Analysis

Systems analysis is the science dealing with analysis of complex, large scale systems and the interactions within those systems. We have a talented team of System Analysts who does requirement analysis, business analysis and system analysis so that all the requirements of the stakeholders can be properly identified and documented so that the designing team can efficiently works on the proposed project.

The very first step is to do the Requirement Analysis of the proposed problem.

Requirement Analysis

The purpose of the Requirements discipline is:

To establish and maintain agreement with the customers and other stakeholders on what the system should do.

To provide system developers with a better understanding of the system requirements.

To define the boundaries of (delimit) the system.

To provide a basis for planning the technical contents of iterations.

To provide a basis for estimating cost and time to develop the system.

To define a user-interface for the system, focusing on the needs and goals of the users.

System Designing -

We have a dedicated group of system developers who works on J2EE platform, Dot NET platform. Our Database designers works on MS Access, SQL Server, Oracle and DB2.

Systems design is the process or art of defining the hardware and software architecture, components, modules, interfaces, and data for a computer system to satisfy specified requirement. One could see it as the application of system theory to computing. Some overlap with the discipline of system analysis appears inevitable.

Steps taken while Designing the Proposed Project are as under: -

Use Case Analysis

Use Case Design

Class Analysis

Class Design

Database Design

Design Of User Interface

Design Element Identification

Design Mechanism Identification

Incorporate Existing Design Element

Operation Analysis

Operation Design

Prototype Design

System Design

Unit testing of the software is done by the designers so that our clients get error free software products.

System Testing

The Test discipline acts as a service provider to the other disciplines in many respects. Testing focuses primarily on evaluating or assessing Product Quality,which is realized through these core practices:

Validate that the software product works as designed.

Validate that the requirements are implemented appropriately.

A good test effort is driven by questions such as:

How could this software break?

In what possible situations could this software fail to work predictably?

Test challenges the assumptions, risks, and uncertainty inherent in the work of other disciplines, and addresses those concerns using concrete demonstration and impartial evaluation. You want to avoid two potential extremes:

an approach that does not suitably or effectively challenge the software, and exposes its inherent problems or weaknesses

an approach that is inappropriately negative or destructive - adopting such a negative approach, you may find it impossible to consider the software product of acceptable quality and could alienate the Test effort from the other disciplines

Testing software is very difficult. How do you quantify the different ways in which a given program can behave?

Implementation

After completion of the project and doing User Acceptance Testing the whole software setup is installed on the user's site as per the instruction mentioned by the client at the beginning of the software development.

Implementation follows the following steps : -

Analyze Run Time Behavior

Execute Developer tests

Implement Design Element

Integrate SubSystem

Integrate System

Verification of Hardware and Softwares on the Client's site.

The purpose of implementation is:

define the organization of the code, in terms of implementation subsystems organized in layers

implement the design elements in terms of implementation elements (source files, binaries, executable programs, and others)

test the developed components as units

integrate the results produced by individual implementers (or teams), into an executable system

Maintenance

Software maintenance is the process of enhancing and optimizing deployed softwar, as well as remedying defects. Software maintenance is one of the phases in the software development process and follows deployment of the software into the field.

The software maintenance phase involves changes to the software in order to correct defects and deficiencies found during field usage as well as the addition of new functionality to improve the software's usability and applicability