3a: Software Documentation

Top/public/assessment/Outcomes/1/1a/csci4230

3a: Software Documentation
Responsibilities for CSCI 4230

Note. Before teaching this course, consult the Response section of the assessment data page for a recent term of this course. Be sure to do what the Response section says should be done.

Assessment of competence
Here, the student is expected to put the ability to use and to demonstrate not only competence in its use but also competence in choosing where to use it. The student's competence is assessed. The setting for student learning In CSCI 4230, students create a project report discussing the product being built, business and detailed requirements, user stories for these requirements, design and architecture details including UML diagrams, test plans, and information about the implementation and use of the system. UML diagrams are created using professional UML modeling tools. Rubric Good. The student report includes appropriate UML diagrams and text to describe the requirements, architecture, and design decisions. The development environment is documented at a level where it could be replicated onto other developer machines, the implementation stack is fully documented, and a description of how to use the application is provided. A traceability matrix or table links requirements to design and to specific tests. Satisfactory. The student report includes appropriate UML diagrams and text to describe the requirements, architecture, and design decisions, but these diagrams and text may have some minor missing details. The development environment is documented, but may be missing some minor details and may require some minor changes to allow it to be replicated. The implementation stack is fully documented, and a description of how to use the application is provided. A traceability matrix or table links requirements to design and to specific tests, covering 80% of requirements. Unsatisfactory. A student's work is unsatisfactory if it does not meet any of the above criteria. Goal At least 75% of students who pass CSCI 4230 are rated as either satisfactory or good. At least 25% of students who pass CSCI 4230 are rated as good.

Assessment of competence

Here, the student is expected to put the ability to use and to demonstrate not only competence in its use but also competence in choosing where to use it. The student's competence is assessed.

The setting for student learning

In CSCI 4230, students create a project report discussing the product being built, business and detailed requirements, user stories for these requirements, design and architecture details including UML diagrams, test plans, and information about the implementation and use of the system. UML diagrams are created using professional UML modeling tools.

Rubric

Good. The student report includes appropriate UML diagrams and text to describe the requirements, architecture, and design decisions. The development environment is documented at a level where it could be replicated onto other developer machines, the implementation stack is fully documented, and a description of how to use the application is provided. A traceability matrix or table links requirements to design and to specific tests.

Satisfactory. The student report includes appropriate UML diagrams and text to describe the requirements, architecture, and design decisions, but these diagrams and text may have some minor missing details. The development environment is documented, but may be missing some minor details and may require some minor changes to allow it to be replicated. The implementation stack is fully documented, and a description of how to use the application is provided. A traceability matrix or table links requirements to design and to specific tests, covering 80% of requirements.

Unsatisfactory. A student's work is unsatisfactory if it does not meet any of the above criteria.

Goal

At least 75% of students who pass CSCI 4230 are rated as either satisfactory or good. At least 25% of students who pass CSCI 4230 are rated as good.