1.

Use the case study provided to complete the table below to calculate the Unadjusted Actor Weight Total (UAW)

Unadjusted Actor Weighting Table:
Actor Type	Description	Weighting Factor	Number	Result
Simple	External System with well-defined API	1
Average	External System using a protocol-based interface, e.g., HTTP, TCT/IP, or a database	2
Complex	Human	3
	Unadjusted Actor Weight Total (UAW)

1(b)

Use the analysis in the case study to complete the table below and then calculate the Unadjusted Use-Case Weight Total (UUCW)

Unadjusted Use Case Weighting Table:
Use-Case Type	Description	Weighting Factor	Number	Result
Simple	1-3 transactions	5
Average	4-7 transactions	10
Complex	>7 transactions	15
	Unadjusted Use-Case Weight Total (UUCW)

1(c)

Calculate the number of Unadjusted Use Case Points (UUCP)

Unadjusted Use Case Points (UUCP) = UAW + UUCW

CASE STUDY

Great State University

Tom, Jan and Julie are majors at Great State University. These students have been assigned aclass project by one of their professors, requiring them to develop a new web-based system to collect and update information about the IS programs alumni. This system will be used by the graduates to enter job and address information as they graduate and then make changes to that information as they change jobs and/or addresses. Their professor also has a number of (database) queries that she is interested in being able to implement. Based on their preliminary discussions with the professor, the students have determined that the only actor is an IS graduate. The database queries and other functions required led them to identify one simple use case, four average use cases and two complex use cases. The technical complexity of the syste m is anticipated to be quite modest. The system will be hosted on a single web server and so not distributed. Response time was thought to be of importance to the IS alums: the students thought they would be intolerant of a slow system. The web site will include blogs, photographs and various other interactive features and so internally processing would be reasonably complex. The design will be unique to the IS program so there will be no need to reuse the software code. The website will use well established style sheets and interface designs and so be relatively easy to install. Ease of use will be critical to the success of this project. Making sure that the information on the web site was up -to-date and complete is also critical: the web site must be concurrent with the universitys other information systems. No special security objectives beyond those already in place for the university are anticipated since no direct access will be pr ovided for third parties. Web browser technology is so ubiquitous that no special user training will be required: users will be intuitively familiar with the web interface and applications such as blogs and calendars that it will provide access to. The stu dent developers experience with object oriented systems development is modest: they felt this might affect the pace of development. Although capable, the ir lead analyst is not yet entirely fluent with the Unified Modeling Language (UML) and the modeling tools associated with it. Despite these issues, they are well motivated and comfortable that - with the guidance provided by their professor - they have established a comprehensive and stable set of requirements. The students have other commitments and wi ll complete the project part -time

. They have chosen to build the web site using C++, the language that they learned in their

Business Application Development class at the university.