Home

About us

Services

Products

Solutions

Partners

Contacts

Language

Home

 
 

PHP Python Solutions

  • open source services
  • open source services | new projects ...
  • open source services | existing project support
  • open source services | project audit support
  • open source services | case studies
  • managed services
  • managed services | colocation services
  • managed services | remote sysadmin ...
  • New Projects

       Submit RFP

    Thank you for considering to get started with CONBY. We have a well-established new project development process that will help you get started with a realistic schedule and an affordable budget. Our new project process involves the following steps:

    REQUIREMENTS INTERVIEW

    First we will want to know what you wish us to deliver -- the goal of the project. Typically, the goal is to develop a new software solution.

    In the interview phase, we will gather as much information as possible to capture the big picture and the key details that define the project. The interview process will involve the stake holders on your side and can be as simple as a few phone interviews, face-to-face meetings, and/or web sessions of other existing products or services.

    Typical Timeline: the interview process typically involves anywhere from 3 person days to 5 person days.

    Deliverables: good mutual understanding of the project.

    SCOPE OF WORK DEVELOPMENT

    The Scope of Work (SOW) represents the most critical documents in the project. The SOW consists of the details of what we are supposed to produce per an established Software Requirements Specifications (SRS).

    If you do not have an existing Software Requirements Specifications document, the SOW development phase will also include SRS development, without which no software should ever exists.

    Typical Timeline: the typical SOW/SRS process can be anywhere from 5 person days (1 calendar week) to 10 person days (2 calendar weeks).

    Deliverables:

    1. Scope of Work Document
    2. Software Requirements Specifications Document
    3. Version 1.0 Base System Requirements (derived from SRS)

    MILESTONE DELIVERY SCHEDULE

    In this phase, we will develop a realistic schedule for the entire project with milestone deliverables and a team will be assigned for project management, development and quality assurance. A project site will be established to allow team communication to be tracked and directed as appropriate.

    Typical Timeline: 3 person days

    Deliverables:

    1. Milestone Breakdown with Planned Schedule
    2. Project Site
    3. Team Roster
    4. Communication and Reporting Procedure

    The Planned Schedule will provide projected date for Alpha, Beta and software Release.

    Note that the team assignments will include Project Manager (CONBY), Project Manager (Your organization), Software Architect, Development Team Members, and QA Team Members.

    The communication and reporting procedure will include how development updates are reported (typically via project board, email lists, by-weekly phone or face-to-face meetings as appropriate).

    INCREMENTAL ENGINEERING

    This is the phase where actual software development takes place. Assigned engineering team will start developing a base version of the product.

    Sample Project Estimations

    Here you will find a few sample time estimates for typical small, medium and large projects we have dealt in the past.

    The Minimal Project (2 wks ~ 1 month) Person Days

    Requirements Interview

    3
    Scope of Work 5
    Milestones & Delivery Schedule 3
    Incremental Engineering Cycles 10
    Total Person Days 21

    The minimum man days are based on our minimum project size requirements.  CONBY does not undertake projects that require less than two weeks of involvement to avoid business goal conflicts.

     

    A Medium Size Project (3 ~ 4 months)
    Person Days

    Requirements Interview

    3
    Scope of Work 10
    Milestones & Delivery Schedule 5
    Incremental Engineering Cycles 40
    Total Person Days 58

    The medium size project runs for 3-4 months with a development team of 2-3 developers, 1 project manager, 1 architect and a 2 person QA team.

     

    A Large Project (6 ~ 12 months)

    Person Days

    Requirements Interview

    5
    Scope of Work 20
    Milestones & Delivery Schedule 10
    Incremental Engineering Cycles 120
    Total Person Days 155

    The large project runs for 6-12 months with a development team of 5-10 developers, 1 project manager, 2 architects and a 3-5 person QA team.

     

     

    CYCLE 1: DEVELOPMENT OF BASE SYSTEM

    The software architect assigned to the project will develop a design document laying out how the base system will operate; what open source technologies will be used; how the system will be divided into the base modules. If the project requires a RDBM database, a database design will be done by the resident DBA. Once the high-level design decisions are made, the development team will start developing modules in parallel and the internal QA team will perform module-level quality assurance tests as appropriate.

    In this phase, you will have access to the work in progress on a project demo site where latest builds are going to be placed for review.

    Once the core functionality is available, the project managers will be given a walk-thru by the system architect. You and your reviewers will be provided a demo version on our server for further review and feedback.

    Based on the review and feedback, a list of fixes and change orders will be established. Change orders will be considered new items and will require adoption in the Software Requirements Document.

    Typical Timeline: project dependent

    Deliverables: base application with core functionalities

    CYCLE 2: ENHANCEMENT OF USER EXPERIENCE

    In this cycle, the end-user interfaces will be enhanced using appropriate cleanup and enhancements available for the chosen platform. For example, for Web applications this phase may require development of client-side scripting, graphical user interface (GUI) components, navigation components, and improved look and feel.

    Typical Timeline: project dependent

    Deliverables: enhanced application with user interface updates

    CYCLE 3: BACKEND AUTOMATION

    In this phase any backend application that needs to be developed to automate the work-flow of the system is developed. The backend automation application includes batch operations, automated backup, and monitoring and notification applications.

    Typical Timeline: project dependent

    Deliverables: alpha version of the entire system

    CYCLE 4: PERFORM SYSTEM-LEVEL QA/QC

    In this phase the system-level quality assurance is performed by running complete functionality test suits on entire system. The results of the test suit runs are analyzed by the development team and necessary adjustments are made. The functionality test suites are available for you and your team to review.

    Typical Timeline: project dependent

    Deliverables: alpha version of the entire system with bug fixes

    CYCLE 5: PERFORMANCE TUNING

    In this phase, the entire system is audited to identify any performance bottlenecks and necessary adjustments are made when appropriate. The entire application is subjected to artificial load to measure performance and operations of various components to ensure stability and reliability.

    Typical Timeline: project dependent

    Deliverables: beta version of the entire system

    CYCLE 6: SECURITY AUDIT

    In this phase, we will review the security implications of the system and perform any necessary adjustment to the software or underlying security infrastructure (OS, firewall device, proxy settings, etc.) as needed to ensure better security.

    Typical Timeline: project dependent

    Deliverables: beta version of the entire system

    CYCLE 7: BUILD A RELEASE & DOCUMENTATION

    In this phase, we will develop the release build and submit version 1.0 design, documentation along with user guide.

    Typical Timeline: project dependent

    Deliverables: release version of the entire system with documentation

    OPERATIONS & MAINTENANCE

    We will train your operations staff to manage the software. If the project requires development of a staff or end-user training module, we will also deliver it in this phase.

    An online issue tracking system will be provided for your operations staff to report issues for resolution. By default, our typical issue resolution phase ends after 30 days of the delivery of the software. An additional maintenance contract is required if we are to provide long-term maintenance and upgrade for the application.

    Typical Timeline: project dependent

    Deliverables: online issue tracking facility for reporting software issues

    LESSONS LEARNED

    Finally, once the application is in use or your operational staff has been handed over the released version of the software, we will request a project debrief meeting where we will discuss the project in a hindsight view point. We will provide you with our technical analysis of the project life cycle management, communication and co-operations of your organization. In return, we would request a review our efforts to identify the good and the bad and possible suggestions to improve in the future.

     

     

     

     


    | Home| About us| Services| Products| Solutions| Partners| Contacts| 

    Copyright ©2004-2019 Conby Information Technology Co., Ltd. All rights reserved.