Today is the day where our eCinema finally roll out after all the thick and thin throughout the 2month plus. We had put in alot of effort on writing the documentations and the implementing the system.
Guys,
GREAT JOB! and WELL DONE!!
The link below is to download our final documentations and system, however it is password encrypted to prevent unauthorised access. Email to ho.wei.zhe@gmail.com for the password.
http://rapidshare.com/files/95645294/HOLTZ_Corp.zip.html
Thursday, February 28, 2008
Sunday, February 24, 2008
Testing Completed
After coming out with the various test cases, finally the testing has been done by our testing team(which is basically everyone). Thanks to all for taking the effort to work overtime to complete the testing, CHEERS!!!
Attached is a copy of our performance testing:
Friday, February 22, 2008
"DEADLY" ER Diagram and Class Diagram
This deadly ER diagram described all our tables in the system and is proudly designed and compiled by Mr. Zhuo Senxian.
This deadly class diagram described all our classes in the system and is proudly designed and compiled by Mr. Tan Boon Chin.
Enjoy..
Thursday, February 21, 2008
Tutorial 5
This Standard specifies the requirements for all SRS used in Defence Equipment.
It has a good set of safety management which clearly defines the Software Safety Plan, Software Safety, Safety Analysis, Software Safety Records Log, Software Safety Reviews and Software Safety Audits
The roles and responsibilities clearly define the different type of authorities needed for authorization and also the various teams needed for the development of the SRS.
The report has a good development plan which includes a detail risk analysis, Verification and Validation procedures, Configuration Management, a good set of design practices and also a detail breakdown of the selection of language and tools.
A detail breakdown of the development process principles, software requirements and the design and coding process. It also clearly defines the testing rules and how the testing must follow the principles of testing.
As for the certification rules, the Software Design Authority shall submit an SRS Certificate of Design to the Design Authority prior to delivery of the SRS to the Design Authority. Acceptance testing shall be carried out prior to acceptance of the SRS by the MOD PM.
It has a good set of safety management which clearly defines the Software Safety Plan, Software Safety, Safety Analysis, Software Safety Records Log, Software Safety Reviews and Software Safety Audits
The roles and responsibilities clearly define the different type of authorities needed for authorization and also the various teams needed for the development of the SRS.
The report has a good development plan which includes a detail risk analysis, Verification and Validation procedures, Configuration Management, a good set of design practices and also a detail breakdown of the selection of language and tools.
A detail breakdown of the development process principles, software requirements and the design and coding process. It also clearly defines the testing rules and how the testing must follow the principles of testing.
As for the certification rules, the Software Design Authority shall submit an SRS Certificate of Design to the Design Authority prior to delivery of the SRS to the Design Authority. Acceptance testing shall be carried out prior to acceptance of the SRS by the MOD PM.
Wednesday, February 20, 2008
Meeting on 19 Feb 2008
Finally after weeks of coding, the program is finally completed. We are entering the testing stage now. In the discussion, we will be finalizing the test plan, test schedule and test cases. We are also in the stage of confirming the sequence diagram.
Below is the minutes for the meeting:
http://www.freewebs.com/holtz311/meeting20080219v03.pdf
Below is the minutes for the meeting:
http://www.freewebs.com/holtz311/meeting20080219v03.pdf
Tuesday, February 19, 2008
Thursday, February 14, 2008
.jpg)
Subscribe to:
Posts (Atom)
.jpg)
