Corporate Software Systems Development || Our Approach

Starting a new project, we first of all make sure that it does not interfere with the current productive activity of the enterprise, by forming the project workgroup (the organizational level) and defining its budget (the financial level). Besides that, we always keep in mind the following basic principles:

• considerate and accurate timing is the key;
• all project efforts are directed toward the achievement of business goals of the enterprise, and all the solutions will be evaluated from this point of view only;
• the process of defining detailed project requirements goes hand in hand with the reorganization of the actual business processes awaiting automation.

Project Phases

The completion of each project includes the following major phases:

1. Mobilization

Work Content: Preparation of requirements specification, evaluation of startup conditions and the extent to which the existing solutions may be utilized. Workgroup forming, budget preparation and project timing. Drafting and conclusion of a contract.

Outcome: Project Requirements Specification, Project Timeline, Contract.

2. Preliminary Designing

Work Content: Data modeling, user interface prototyping, development of protocols and interfaces of interaction with conjugate systems. Drafting of project documentation.

Outcome: Draft Design, Systems Layout, Software Platform Requirements, Security and Access Levels Specification, Manning Requirements.

3. Detail Designing

Work Content: Development of software components (data patterns, menu modules, forms, reports, etc.), phased assembly and testing, revision of project documentation.

Outcome: Project software, Full Installation Package, Documentation (User Manual, Admin Manual, Programmer's Guide).

The installation package includes a complete set of software required for the installation and initial setup of the system.

4. Deployment

Work Content: System installation, customization of reference data, users and support personnel training. Initial data loading, testing, overpatching requirements specification.

Outcome: A working system, Overpatching Requirements.

5. Operation Testing, Commission

Work Content: Project software revision, overpatching based on the requirements specified in the course of deployment and operation testing.

Outcome: Revised Project Software, Patched Installation Package, revised Documentation.

6. Commercial Operation

Work Content: Technical support, error correction, hotline maintenance. Further development in accordance with changing requirements and own plans for development.

Logical and Physical Designing Concepts

The logical layer includes requirements and specifications formulated in terms of processes, entities, links and notions of a particular data domain, independent of specific features of implementation.

The key system components distinguished at the logical layer are subsystems and services. The division of a corporate system into subsystems corresponds with the highest level of functional hierarchy, describing the system requirements that directly answer the goals, objectives and enterprise activity functions, such as Referenced Data Maintenance, Contractual Work, etc.

Services represent the highest level of functional hierarchy of intrasystem and official requirements (Access Levels and Security, Auditing, Preparation and Printing of Reports and Document Sheets, etc.).

The physical layer includes requirements and specifications formulated in terms of modules, tables, constraints, triggers, COM objects and the like, corresponding to program components and data objects.

This development method is based on our own unique experience as well as a number of recognized market standards (Oracle Custom Development Method, Rational Rose UML/Unified Rational Process, 4FRONT Deloitte&Touche, SADT/IDEF).

« back