FAIL (the browser should render some flash content, not this).
 
Curosys Software methodology

Curosys solutions methodology is process centric methodology. Depends on the customer requirement curosys follows various methodologies. One of the popular methodology is standard Software Development Life Cycle (SDLC) process with 6 distinct phases during the execution of a project.

Project Management & Review Activities forms the outer layer for the whole process for effective management control and successful execution of the project.

Schematic of the proposed Process Flow for the System Design, Development & Deployment of an enterprise grade software project is given below. A modified version of Waterfall Model is followed for the project.

Software Process Models

To solve real time complex business problems, a software engineer or a team of engineers must incorporate a development strategy that encompasses the process, methods, and tools layers. This strategy is often referred to as a Software Process model.

A software Process model is chosen based on the nature of project and application, the methods, and tools to be used, and the controls and deliverables that required.

Software development process
1. Software Requirements Analysis and Management

After the initial step of team formation, we do a thorough needs analysis of customer requirements including determining needs (elicitation), addressing how those needs need to be addressed (triage) and documenting the desired external behavior of the systems (specification) Allocated Requirements Review Managing Systems Requirements Allocated to Software Policy

2. Software Project Planning

Planning is a critical phase, which involves creating high-level architecture, delivery and deployment schedules for software development, information and capacity architecture, and third-party integration.

  • Software Development Plan
  • Software Estimates Procedures
  • Project Schedule
  • Software Life Cycle Definition
  • Software Planning Data
  • Software Project Activities and Commitments
  • Software Engineering Facilities and Support Tools Plan
  • Managing Systems Requirements
3. Software Project Tracking and Oversight
  • Revision of Software Development
  • Plan Peer Review Plans
  • Change Requests and Problem Reports Procedure
  • Formal Reviews of Selected Milestones
  • Project Tracking and Recording Procedures
4. Software Quality Assurance
  • Software Quality Assurance Plan
  • Policy for Implementation of SQA
  • Deviations in Software Activities and Software Work Products Procedure
  • SQA Participation Procedure
  • SQA Reports
  • SQA Reviews Procedure
5. Software Configuration Management
  • Activities Plan
  • Configuration Items/Units Status Review Procedure
  • Standard Software Configuration Management Reports
  • Baseline Audits Procedure
6. Testing

After the various components are developed, they are integrated and rigorously tested as a complete solution. Application behavior is compared with the initial specifications and any deviations are identified and corrected.

  • Specification Testing
  • Functionality Testing
  • Integration Testing
  • Stress/Real-world Testing
7. Implementation

After the project is completed, it is deployed across an enterprise by working closely with its internal IT team and training is imparted to the end-users of the system.

  • Enterprise-wide Deployment
  • End-user Training
  • System/Helpdesk Training
  • Documentation Handover
8. Maintenance

Our maintenance phase covers system health maintenance including database, application and network maintenance. Required application feature enhancements are planned at this stage, and are developed and executed as and when appropriate.

  • System Health Maintenance
  • Feature/Application Enhancements