Use-case Driven

Use-cases capture functional requirements for the user. The term user represents someone or something (such as another system outside the proposed system) that interacts with the system being developed. Combined, use-cases make up the use-case model, which describes the complete functionality of the system.

This model replaces the traditional functional specification of the system. The use-case model answers questions such as, "What is the system supposed to do for each user?" The use-cases bring together business values and technical functions. In this respect, the system must incorporate usable functions while at the same time providing value to the users.

Based on the use-case model, developers create a series of design and implementation models that realize the use-cases. The developers review each successive model for conformance to the use-case model. The testers test the implementation to ensure that the components of the implementation model correctly implement the use-cases. The development process follows a series of workflows that derive from the use-cases.

Architecture-centric

The architecture stems from the needs of the stakeholders as reflected in the use-cases. Software architecture is depicted as the system's components are built. Architecture is a bird's eye view of the entire design; the important characteristics are more visible while details are to the side.

The determination of areas that are significant rests with the personal judgment, which comes with experience. PTI engineers possess a high degree of technical skills that are invaluable to development projects. When allocating our engineers to projects, the project manager identifies the competencies of our engineers and then matches them with the required competencies of the project.

By ensuring that all team members understand their roles and priorities, you create the foundation for team confidence and project success. The value of the architecture depends on the people assigned to the task.

PTI's project management process helps to focus on the right goals, such as being understandable, scalable and reusable. The architecture is also influenced by many other factors, such as the platform, the software to run on (e.g., computer architecture, operating system, database management system, protocols for network communication), the reusable building blocks available (e.g., a framework for graphical user interfaces), deployment considerations, legacy systems, and nonfunctional requirements (e.g., performance, reliability).

Iterative and Incremental

Because software development projects can become very complex, PTI divides work into smaller, more manageable assignments. These assignments are iterated throughout the workflow, leading to incremental progression and, ultimately, project completion.

Iterative development reduces risks in several ways. This approach addresses the highest risk items at every stage in the lifecycle. Because each of the iterations ends with an executable release, the development team stays focused on producing results, and the end-users have continuous involvement and feedback. Frequently checking the project's status ensures development stays on schedule. An iterative approach also makes it easier to accommodate tactical changes in requirements, features, or schedule.