Page: 1 23

Our Hallmark

Another Project Delivered on-time and on-budget

The Trilliant Group is a boutique consulting engineering firm specializing in IT Energy Best Practices, Custom Solution Development, Storage Consolidation, and Project Management.

Development

All development activities for the prototype were conducted off-site. Consequentially, in order to facilitate good communications, a weekly status email was sent to all involved parties to supplement occasional conference calls that were scheduled.

Governed by Trilliant Group’s belief that the key to successful software development projects is good planning, most initial activities were simply discussions between the Trilliant Group software engineers and project lead. This tactic allowed for re-examination of the design concepts by applying specific use-case scenarios. A detailed project development timeline was then prepared. Once any refinements were identified and approved by the client, actual code development began.

Development was broken down into segments. System maintenance was addressed first, including login activity. This allowed for the development of shared Business Logic and Stored Procedures that would be refined and utilized for other prototype pages. Additionally, it allowed for creation of the overall Theme and access procedures that would be utilized throughout the prototype. As purely administrative tasks, these activities were only tested for very high-level functionality. The administrator could always employ direct database modification if necessary.

Project Management was addressed second, being built upon the table maintenance functionality to provide the data required for Content. This provided a scenario in which to test the access control functionality, since all other system maintenance functions were inaccessible to everyone except a system administrator. This activity was more complex and also provided the ability to test other procedural code and business logic.

Content was addressed next. As the primary user interface, most functionality existed in this activity grouping. Access control to the Folder Tree was limited to Projects for which the logged-in user was associated. Display of content in the Grid was not limited, following the typical Windows File Manager paradigm. A user could choose to drill-down on associated metadata in the grid, where Group settings for “No Access”, “Read”, “Modify” and “Delete” were implemented.

Top of Page

Finally, a basic Content Search facility was developed that was limited to Content Name and Content Metadata Name. This area would provide the platform for the client to add various search mechanisms and also to “plug in” some of their internally developed analysis tools.

Software engineers were responsible for unit-testing their code before a build was released for general QA testing. All functional defects were identified, fixed and regression tested. A list of all remaining cosmetic defects was maintained in order to address them at a later time.

QA Testing focused on entering real-world client data. It also included creating and testing initial product installation scripts. Database creation also included a complete Content Template structure, patterned after the current folder structure in use by the client.

Basic documentation was generated covering User Guide, Administrative and Installation. A client CD was prepared including a MSI installation bundle.
Test, Acceptance & Integration
The delivered prototype was installed in the client’s test lab, validating the installation scripts and procedures. Integration with other systems, especially the Exanet NAS device was also confirmed. The client software engineering lead inspected the developed code to assure that it met the desired design objectives and would be easy to maintain.

General user testing by the client’s IT staff was conducted to determine that the prototype met the desired functional requirements. At this point, final acceptance testing was conducted by the client on the basis of a comparison of actual against requested performance (functional objectives) and of a verification of time and budget objectives.

Succesful Deliverable

The prototype product was delivered on time and on budget. The client’s code and design review was characterized by comments like “it is exactly what I would have done given the time and opportunity”. Since the client audience was principally their IT department, their participation in the design process was crucial to the success of this project. This prototype will provide a solid basis from which they will develop the production product. Trilliant Group was contracted for another project shortly thereafter, which is always a welcome sign that we met both our client’s requirements and expectations.

Page: 1 23 Our Hallmark Another Project Delivered on-time and on-budget The Trilliant Group is a boutique consulting engineering firm specializing in IT Energy Best Practices, Custom Solution Development, Storage Consolidation, and Project Management.	Development All development activities for the prototype were conducted off-site. Consequentially, in order to facilitate good communications, a weekly status email was sent to all involved parties to supplement occasional conference calls that were scheduled. Governed by Trilliant Group’s belief that the key to successful software development projects is good planning, most initial activities were simply discussions between the Trilliant Group software engineers and project lead. This tactic allowed for re-examination of the design concepts by applying specific use-case scenarios. A detailed project development timeline was then prepared. Once any refinements were identified and approved by the client, actual code development began. Development was broken down into segments. System maintenance was addressed first, including login activity. This allowed for the development of shared Business Logic and Stored Procedures that would be refined and utilized for other prototype pages. Additionally, it allowed for creation of the overall Theme and access procedures that would be utilized throughout the prototype. As purely administrative tasks, these activities were only tested for very high-level functionality. The administrator could always employ direct database modification if necessary. Project Management was addressed second, being built upon the table maintenance functionality to provide the data required for Content. This provided a scenario in which to test the access control functionality, since all other system maintenance functions were inaccessible to everyone except a system administrator. This activity was more complex and also provided the ability to test other procedural code and business logic. Content was addressed next. As the primary user interface, most functionality existed in this activity grouping. Access control to the Folder Tree was limited to Projects for which the logged-in user was associated. Display of content in the Grid was not limited, following the typical Windows File Manager paradigm. A user could choose to drill-down on associated metadata in the grid, where Group settings for “No Access”, “Read”, “Modify” and “Delete” were implemented. Top of Page	Finally, a basic Content Search facility was developed that was limited to Content Name and Content Metadata Name. This area would provide the platform for the client to add various search mechanisms and also to “plug in” some of their internally developed analysis tools. Software engineers were responsible for unit-testing their code before a build was released for general QA testing. All functional defects were identified, fixed and regression tested. A list of all remaining cosmetic defects was maintained in order to address them at a later time. QA Testing focused on entering real-world client data. It also included creating and testing initial product installation scripts. Database creation also included a complete Content Template structure, patterned after the current folder structure in use by the client. Basic documentation was generated covering User Guide, Administrative and Installation. A client CD was prepared including a MSI installation bundle. Test, Acceptance & Integration The delivered prototype was installed in the client’s test lab, validating the installation scripts and procedures. Integration with other systems, especially the Exanet NAS device was also confirmed. The client software engineering lead inspected the developed code to assure that it met the desired design objectives and would be easy to maintain. General user testing by the client’s IT staff was conducted to determine that the prototype met the desired functional requirements. At this point, final acceptance testing was conducted by the client on the basis of a comparison of actual against requested performance (functional objectives) and of a verification of time and budget objectives. Succesful Deliverable The prototype product was delivered on time and on budget. The client’s code and design review was characterized by comments like “it is exactly what I would have done given the time and opportunity”. Since the client audience was principally their IT department, their participation in the design process was crucial to the success of this project. This prototype will provide a solid basis from which they will develop the production product. Trilliant Group was contracted for another project shortly thereafter, which is always a welcome sign that we met both our client’s requirements and expectations.
	Home \| Site Map \| Privacy Policy \| Code of Ethics \| Contact Us All contents Copyright © Trilliant Group, Inc. 2003 - 2007. All rights reserved.