Software Development

MySepadu has been engage in Software Developments Services for the past 15 years (Learn more..). Being as an MSC Status company we acknowledge that the Software Development Capability and Maturity is important to the success of the software project. We also realize that Project Management is the most critical component that contribute to the success of the project. Apart from that, Software Testing is also one of the crucial area. We also understand that, after sales support is also one of the key factor for the success of the organization.

Our Software Project will be managed by professional and certified Project Manager (PMP) accountable for managing at least 3 teams - SQA- Software Quality Assurance, SD - Software Developer and TS - Technical Support.

The role of the SQA, SD and TS

The main role and functions of the SQA is to deal with the user to ensure their expectations achievable. SQA will help PM on preparing the requirements study and documentation. SQA will deliver the requirements to the Systems Analyst from the SD team. SD will perform Systems Analysis and Design Study and the SQA will always liase with the user in every stage of communications between SD and the SQA. SD will not deal direct with the user, this is to ensure that the SD team are not under direct pressure from the user. SQA will analyse and filter any request from the user before given it to SD. SQA will also perform the initial test before proceeding to the user test. SQA will also prepare the test script and user documentation.

TS will be responsible on matters related to servers, networks, desktops and the operating systems related application such as performance and security. TS will ensure the compatibility between the application developed and the hardware.

Requirements Analisis Plan.

The Requirements analysis Plan that confirm to the standard of the Capability Maturity Model Integration (CMMI) Level 3 will be performed and the Requirements document will be published to be endorsed by the steering committee. At this stage we already have the generally defined process. The requirements process will cover the development and analysis of the requirements and its verification. This will also include the identification of the systems functions and their interfaces.

We will start with the initial requirements which will be extracted from the tender specification. The requirements will be further analyzed and each requirements will be attached with an attribute - Priority, Risk etc.

Change Management Plan.

The requirements may change at any time during the development cycle. We still allow the changes to happen before the Final Acceptance Test. For every request for the requirements change it must be documented and analyzed by the SQA before present it to the Steering Committee. The requirements change must get approval from the steering committee. The approved requirements change will then be given to the SD team by SQA.

Risk management Plan.

The Risk factor will be identified during the requirements analysis and it will be attached to each identified requirements. The risk will be discussed in detail during steering committee meeting and the action plan for each risk will be identified.

Quality Management Plan.

The Quality Management Plan is developed base on users satisfaction attribute that was originally developed by the Hewlett-Packard (HP) - FURPS (functionality, usability, reliability, performance and service). We will be using the attribute during the User Acceptance Test (UAT).

Systems Analysis and Design (Software Development Methodology)

The project will be developed base on ‘spiral' developement methodology and ‘rapid prototyping'. This means the systems developement will be started straight away when the basic requirements has been identified. The prototype will be developed from the requirements and the actual systems will then be developed from the prototype. The developments will involve many cycle of the requirements-prototype-actual systems developement cycle. Each indepth cycle will ensure the completeness of the systems requirements and maturity.

Training and Technology Transfer Plan.

Training together with the user and systems documentation will be given as below :

End User Training

The formal training will be given twice - before User Acceptance Test (UAT) and after the UAT before the implementation.

The informal training will be given continuously to ensure the smooth runnning of the delivered systems as long as the systems is under the maintenance contract.

Systems Administrator Training

Data Migration Plan.

Data Migration plan will be performed according to the requirements.

Implementation Plan.

Project Schedule

Task duration.

Project Monitoring Plan.

The report will be produced for the purpose of project monitoring will be as below :

Weekly Report - Project Development.

Monthly Activity Report.

Monthly Project management report.