Sunday, December 19, 2010

jAPS 2.0 Project Life Cycle

Regarding to the different phases of platform life cycle, there are many stakeholders who interact with the platform:
Conception and design
The flexibility of the jAPS 2.0 Platform allows to design systems, consistent with project objectives and customer needs. User interface and contents organization can be designed with any constraint.
jAPS 2.0 Platform separates the Java development context (additional modules, integrations and customizations) from the presentation development (graphic templates, markup, CSS). Developers with different skills can work separately, without any interference and without having to move into unknown domains.
The configuration parameters of jAPS 2.0 Platform, in connection with the installation environment (development, test, production) are managed by the system with the aim to make easier customization, flexibility and simplicity of management.
Contents, services and system management are executed through an easy, intuitive and accessible back-end interface. Contents update and web pages organization don't require technical skills. There are no barriers for people with disabilities. New back-end applications can be integrated in the same graphic and functional context.
jAPS 2.0 allows to achieve the desired objectives in term of design, accessibility, quality and customization with no constraints. Usage-centered design is the approach model used to design user interfaces. jAPS interfaces, based on a focus on user intentions and usage patterns, make easier interaction between user roles.
Source code quality, modular design, layered architecture, usage patterns make possible platform evolution with high efficiency in relation to the complexity of the targets.

No comments: