You are on page 1of 3


– To apply software development techniques (Design, Implementation, Testing)

– Expose students' to technical documentations
– Expand students' ability to express ideas effectively through critical analysis,
discussion, and writing
– Learn how to work in team and resolving conflicts

How the class works:

– Given the requirements
– Create a software design, standards (team work, coding, etc), and guidelines
– Develop testing plan
– Start writing the documentations
– Implement your design
– Test
– Go to grading session.

– Working Software
– Coding Standard
– On top of each class, procedure, function, and method there should be
informations below:
– Method/Procedure/Class Name
– Description
– Calling Sequence
– Input Parameter
– Output Parameter
– Errors Conditions Tested
– Error Messages Generated
– Original Author
– Creation Date
– Modification Log: Who When Why
– Coding Standards Met: “signed”
– Testing Standards Met: “signed”
– History → Have a log book that record all meetings that occurred (meeting
minute). At the end of the record (meeting minute), there should be list of
tasks that are assigned with the due date
– Data Element Dictionary → for every variables declared in your code, should
be recorded. This should include variable name, data type, defined @,
local/global, used for
– Errata Report → Report all errors that you have in your coding and
– Software Documentations
– Three major section:
– User Guide → Help user in using the software
– Development Guide → Help other developers who work on the software
– Design Documentations
– Source Codes
– Test Plan → Describes the testing philosophy that you employ and the
purpose of each test run.
Test # Purpose Results as Expected? Problems/Notes

– Concurrent Software Development Steps
Step Code Development Test Planning Documentation
Requirements/Standards Define Acceptance Outline
High Level Design Define System Testing Draft
Detailed Design Define Integration Testing Draft Revision
Refinement Define Unit Testing and Finalize
Refined Integration
Code Development Unit Test Verify
Code Polishing System Test Make it look better

– Software Project 300 pts (41%) → if your software doesn't work at all then you
get zero regardless of the documentation. There will be 4 (four) grading session.
The points for each session could be different, but all points from each session
will add up to 300 pts
– Peer Evaluation 100 pts (13%)
– Presentation, Team Management, and Design 100 pts (13%)
– Midterm exam 100 pts (16%)
– Instructor Evaluation 50 pts (7%)
What I Expect:
– Read email, try to find out if there are changes (There could be changes without
any limitations)
– Bring questions to the class
– Design your program BEFORE writing nay code
– Test your program BEFORE come to the grading session
– Meet or exceed due dates
– Meet or exceed all requirements
– Attend at least the some part of the class time

Team Assignment:
– Project Leader
– Lead the whole team. Make sure every coordinator doing their job well.
– Design and Implementation Coordinator
– Manage the design process, documentations, and implementation tasks. Keep
track commitment of others
– Test Coordinator
– Make sure all the testing are done. Develops testing documentations. Keep
track commitment of others
– Documentation Coordinator
– Ensure the documentations are professional looking and everyone submits
their documentations. Keep track commitment of others
– Code Coordinator
– Responsible to ensure all the code fit the standards, clean, and organized. Keep
track commitment of others

How to get A in the class

– Listen to your instructor
– Teamwork, one vision
– Ask questions if you have any concerns/doubt/anything (but don't ask your
instructor or anybody to do your work)
– Starts early, don't wait
– No playing