SOFTWARE DEVELOPMENT PROCESSES

Our development processes ensure that our customers have full project transparency, control over the production process, and predictable deliverables at each project phase.

We offer our customers two software delivery models: remote software development and combined on-site/ remote development with the local team.

Axmor Software offers you flexible price/project plans to suit your individual needs and capabilities.

Development process at Axmor

Phase	Activities	Deliverables
Analysis	Create a business case Capture requirements Scope the system Design a high-level architecture Identify critical risks Formulate a bid which includes resources, time, equipment, staff and cost	Project status: System requirements gathered. Documents: Proposal SRS (Software Requirements Specifications) Project Plan
Design	Create an executable architectural baseline Create a detailed plan for the Implementation phase	Project status: System design defined. Documents: SAD (Software Architecture Document). Identifies the software components and describes components design
Implementation	Coding defined software components Maintain the integrity of the system architecture.	Project status: System development in progress. Documents: Status Reports
Testing	Develop a Test Plan Perform Testing according to Test Plan Correct defects	Project status: System testing in progress. Documents: Test Plan Test Reports
Deployment	Prepare the users site for the new software Tailor the software to operate at the users site Create user manuals and other documentation Provide customer consultancy	Project status: System deployed. Documents: User manuals Other user supportive documentation
Support	Monitor system performance Maintain the integrity of software and hardware Create user manuals and other documentation	Project status: System operation support in progress.

Typical project/iteration flow:

• The customer provides a high-level specification on what should be done via specification document (the most efficient form), chat or phone conversation.
• Axmor analyzes the requirements, and develops the detailed specification overview.
• The customer makes necessary adjustments to the specifications prepared by Axmor. We update the specifications accordingly and prepare a project plan (schedule and workload).
• After project proposal approval, the development begins. During development, the project scope can still be updated if required.
• Axmor performs internal Quality Assurance and testing activities, and passes the completed deliverables to a customer.
• Upon project completion, Axmor engineers remain available for project support. Whether the project requires migration to a newer platform version, or an application needs upgrading to meet changing business needs, Axmor specialists are readily available.

Project Planning

Each step of the software development has its project plan (in Microsoft Project format); the master project plan contains all current and planned tasks and assignments of team members.

Project Environment

When needed, Axmor sets up a CVS system to coordinate project artifacts.

When needed, Axmor sets up remote access (e.g. terminal services) to allow demonstrations or testing of the software in the customer’s environment.

Customer communication/ Project tracking:

• Daily emails/chats/phone calls to discuss technical issues (requirements, architecture, etc).
• Weekly emails/chats/calls to discuss the current project status.
• Monthly or on demand emails/phone calls to discuss the partnership, oversee the past month and make decisions on the development process, project configuration, etc.
• Submit periodical or on demand project updates (time spent reports, update of the project plan, weekly status reports).

Quality Assurance

Quality control activities are performed continually throughout all project phases to verify that project management and project deliverables are of the highest quality.

At Axmor, we use:

• Templates & Guidelines

  Standardized templates are used for all types of project documents. Using templates allows creating comprehensive easy-to-read documents. Guidelines are used in the development process to assist in creating quality project deliverables. Guidelines can be cross-industry and corporate.

• Formal Testing & Acceptance

  To ensure high quality of deliverables, testing and acceptance criteria for every deliverable and project phase are established. Acceptance criteria must comply with industry and corporate guidelines.

• Peer Reviews

  In a peer review, colleagues of the creator of a particular software work product examine the product to identify defects and correct possible flaws.

  All interim and final development work products are candidates for review, including requirements specifications, architecture design, or source code.

• Change & Configuration Management

  Configuration Management is a supporting process whose purpose is to identify, define, and baseline items; control modifications and releases of those items; report and record status of the items and modification requests; ensure completeness, consistency, and correctness of the items; control storage, handling, and delivery of the items. By implementing Change and Configuration Management practices, quality of the deliverables is controlled.