1.3. Operational Setting

There are two operational settings for the Calendar Tool: (1) normal use as a functioning software system; (2) use as an example in software engineering courses.

The Test Tool is primarily intended to be used for the Cal Poly Computer Science department. It can also be used for other academic departments at Cal Poly as well as other universities or organizations that may find this tool useful. The physical setting where this tool will be installed will be on a department-level host computer which also stores a shared database, securely posted untaken tests, securely posted graded tests, publicly available practice tests - with selectable limitations on who the "public" may be. The Test Tool may also be installed on personal computers which tests are generated, graded and posted to the server, in dedicated test-taking rooms that include a single control machine for proctoring tests and slave slient machines for students to take tests, and personal student computers where they can do practice and take-home tests.

There is a single primary customer for the Test Tool, and he is representative of customers in a particular university department: Professor G. Fisher of the Computer Science department at Cal Poly. As such, the tool's requirements reflect the point of view of the customer base, including their work setting. Although the customer will try to make features general when reasonable, the tool will include setting-specific features the custermer feels are necessary.

As an example of its use, this tool has been designed for Professor G. Fisher in undergraduate and graduate software engineering courses at Cal Poly University. These courses are two-quarter sequences that cover standard aspects of software engineering, with emphasis on the practical application of formal methods. For the most part, the concepts covered in these courses, and hence the concepts embodied in the Test Tool, are mainstream software engineering. Other instructors may therefore find the Test Tool and its development artifacts useful as course examples.






Prev: personnel | Next: impacts | Up: intro | Top: index