1. Web page creation module (First increment)
2. web page authoring module (First increment)
3. web page selection (First increment)

1. Bulletin board module (First increment)
2. Instructor Email module (Second increment)

1. Search module (First increment)
2. Translation module (First increment)
3. Fetch module (First increment)
4. On-line help (Second increment)

1. Authentication (First increment)
2. Locking (First increment)
3. Time stamping (Second increment)
4. Link updating (Optional increment)
5. Modification module (Optional increment)
6. Statistical log (Optional increment)

Figure 2.3.1 Product Design mile stone chart

From the product design phase, the real funtional codes can be made in each incremental phase. The developer can work in parallel, bottom-up (object-oriented). The first increment is for essential capabilities in the ICTM. The first increment should be completed by ?

Figure 2.3.2 First Increment mile stone chart

The second increment is for the desirable capabilities in the ICTM. This should be completed by Apr. 29, 1998.

Figure 2.3.3 Second Increment mile stone chart

3.1 Organizational Responsibilities

The primary users of this system will be students and instructors from the French and Italian department; however, the primary instructor of each ICTM course may allow participating instructors, from Paris for example, to contribute material to the instructional site. The system administrator will likely be part of the USC UCS (University Computing Services) and the client supervising the ICTM project will be from the Center of Excellence in Teaching. A project team from CS577a will be responsible for architecting the ICTM system while a project team from CS577b will be responsible for implementing it.

3.1.1 Global Organization Charts

Figure 3.1.1 Global Oragnization Chart

3.1.2 Organizational Commitment Responsibilities

Any additions or modifications to the ICTM should first be approved by all ICTM stakeholders next semester and should be done as early in the developmental process as possible. Of course, they should make sure that any extra functions added should not require modification of the operation concept definition.

The UCS is responsible for this change in system scope and plan. In addition, for authentication purposes, UCS has the responsibility of providing stability of system inspite of changing.

Each member of ICTM development for this change in system scope and plan. In addition, the CS577b developers next semester are also responsible for no performance decrase of the system following any significant changes to the system.

3.2 Development Responsibilities

A team (four students) in CS577a had the responsibility for planning the requirements and architecture of the ICTM system. Next semester, a team of five graduate students enrolled in CS577b will be responsible for the actual development of the International Cross-Cultural Teaching Model. The team will specify products and implement the ICTM software.

Please, refer to 3.2.2 Staffing

3.2.1 Development Organization Charts

Figure 3.2.1 Development Organizational Chart

The software development plan calls for a team consisting of five CS577b students to be assigned to the project.

1. Project Manager

   One student will take on the responsibilities of the project manager, who will be responsible for monitoring project progress, ensuring consistency among the team members' artifacts, resolving issues and risks, and maintaining proper contact and communications with the customer.

2. Software Engineer

   Two students will take on the role of software engineers whose primary responsibilities will include analyzing and product design specification, and detailed design specification, and writing codes.

3. Test Engineer

   Another student will assume the role of the test engineer who will be responsible for writing the test plan and performing various tests to ensure quality and consistency of the system.

4. System Engineer

   The fifth student team member, the system engineer, will oversee the requirements analysis and user's manual documentation.

The organizations for ICTM need training(internal) for ICTM team member as well as training(external) for administrator, customer, and instructor user.

The CS577b students assigned to this project are expected to have a strong programming background in Java, Perl, HTML, and CGI as well as a basic knowledge of Unix. Background in French is unnecessary since the only French put to use is via the translation feature which is done through an on-line provider.

Instructor users will be learned for World Wide Web and internet. Also they will be trained for web manipulation including Webpage authoring, selection, and creation as well as Tools containing Search, translation, and fetch. Student users will be learned for access the ICTM via interet web browser. In addition they will be trained the ICTM student site functions including Bulletin board and intructor email as well as tools such as search and translation.

4.0 Approach

4.1 Risk Management

The ICTM's primary process model is the Spiral Model. The most important distinction between the spiral model and other software process models is the explicit consideration of risk in the spiral model. Among critical risks, unrealistic schedules and budgets can be managed with detailed estimates of multisource costs, schedule, and software reuse. To help avoid developing the wrong user interface, we can use task analysis, prototyping, and create scenarios. For the gold plating risk, we should do prototyping, cost-benefit analysis, and calculate design costs. The first step is to reduce software risk and to identify the project's critical risk items. The second step is to present a plan for resolving each risk item and maintain a monthly list of critical risk items, plans, and results. The third step is comprised of each previous month's rankings and status. Then the final step is to initiate the appropriate corrective actions.
Please refer to the risk analysis of the Feasibility Rationale (Section 5.0) for a list of top risk items.

A risk-driven waterfall strategy will be embedded within the spiral model to accomodate the two incremental development phases of the ICTM. The first incremental release will contain the primary core capabilities which is comprised of functionality available to both users as well as those specific to the instructor users: web page creation, web page authoring, web page selection, a bulletin board, logging in, and fetching multimedia files. The second incremental software release will contain the secondary core capabilities which is primarily comprised of functionality that will be available at the student site: searching, translation, time stamping of pages, and emailing the instructor.

4.2 Development Phases

The ICTM uses the Spiral Model in development process. With the knowledge from previous phases, every phase of the development process is made. Spiral model usage consists of objectives, constraints, alternatives, risks, risk resolution, risk resolution results, planning for the next phase, and committment. But for incremental development, the risk-driven model is used.

The spiral model for the ICTM consists of plans and requirements, product design, and two incremental developments. Each increment contains detailed design, coding, unit test, updating, integration and test.

4.2.1 Plans and Requirements Phase

For the three primary stakeholders(user, customer, and developer), the purpose of this phase is to establish top-level life-cycle plan includinng milestones, resources, responsibilities, schedules, and major activities for the ICTM. We used WINWIN for negotiations as well as Rose for UML under object-oriented environment. These are used to develop the system. The LCO is top-level definition from these. The next step, LCA is made from LCO. The LCA is the definition of the system and software architecture.

The plans and requirement phase produce WinWin negotication Report; Operational Concept Description Document; System Requirements Definition Document; Software Archtecture Definition Document; Software Development Plan document; Feasibility Rationale Document; Basic Prototype and its document to provide preview for customer.

4.2.2 Product Design Phase

This is the phase for determination, specification, the review of hardware and software architecture for the ICTM. The purpose of product design is to specify how to implement LCA. To reduce high risks in product design is recommended. The prototype is expanded to cover this phase. Also COCOMO may be used to estimate the cost and schedule during this phase.

In the product design phase, developer can use top-down strategy. The most important thing which developer have to do is to prepare everything needed to make real codes in each increment.

In addition, valid and approved software requirements specificaion is needed -- for performance, interface specifications for completeness, consistency, testability, and feasibility. Also the ICTM component hierarchy should be validated and approved.

4.2.3 Incremental Development Phases

From the product design phase, specific unit codes can be made in this phase. The developer can use bottom-up(object-oriented) strategy. The product design uses a top-down strategy for top module definition while the incremental development phases (except integration and testing) use bottom-up strategies for the parallel development of each unit.

This phase consists of detailed design, programming (coding), unit test, updating, integration and test. Each program module is created in this phase.

4.2.3.1 Detailed Design

Detailed design specification is made and verified. The tools to program a unit should be approved by all developers. The following elements may be needed:

1. Physical and logical data structure through field level
2. For each routine, purpose, assumptions, sizing, calling sequence, error exits, inputs, algorithms, and processing flow.
3. Data processing resource budgets(timing, storage, accuracy)

4.2.3.2 Coding(programming)

Unit computations using normal values as well as singular and extreme values are included. Also all unit input and ooutput options, including error messages or branch options, can be contained.

4.2.3.3 Unit Testing Plan

All designed and programmed unit codes are tested.

Essential Capabilities Increment(First increment)

When integrating, the developer has to verify the satisfaction of software requirements and demonstrates acceptable ICTM software products.

First, each component should be integrated and tested. Second, if some errors are found, then tester should inform the programmer and error unit should be not only backtrack but also redesign and write code.

Third, after each component has been successfully integrated, the ICTM software integration will be proceed.

Each component integrating

4.2.4 Release

The release is final in formal phase. The system installation phase can follow this phase and system maintenance should follow this.

4.3 Reviews

The objective of each review is to determine whether or not the project is ready to proceed to the next development phase. The ICTM has four cycles. The first cycle is plans and requirements, the second cycle is product design, the third cycle is the first inclemental development, and the fourth cycle is the second incremental development.

4.3.1 Plans and Requirements Review (PRR)

This is scheduled to be at the end of the Plans and Requirements phase. The objective of the PRR is to ensure that all stakeholders agree with and satisfy the system plans and requirements. In this, participants are users, customers, and developers

4.3.2 Product Design Review (PDR)

This is scheduled to complete Product Design. The objective of PDR is to ensure that the products designed are satisfactory and that all high-risk elements of the software project have been identified and resolved. Participants are users, customers, and developers

4.3.3 Reviews in Increments

The major documents consists of following:

Configuration management(CM) is the process which controls the changes made to a system and manages the different versions of the evolving ICTM.

During developing the ICTM, many documents are produced. Many of these are technical working documents presenting developing idea. A key task of the configuration management planning process is to decide exactly which item are to be controlled. The ICTM development plan, Product Design specification, Unit Detailed Design and Code, Software Product (ICTM software) will be maintained as configuration items. However all documents which may be necessary for future system maintenance need to be made.

Managed versions may be assigned identifiers automatically when they are submitted to the ICTM. Versions of components must be checked out explicitly for change. The identifier of the engineer making the change is recorded. All of the changes made to a particular system or component may be recorded and listed.

The ICTM may need to use a CASE tool in configuration management.there are several CASE tools available to support this process. For Unix platform, the most widely used version management systems are SCCS(Rochkind, 1975) and RCS(Tichy, 1985). The CS577b development team should decide to use which version.

4.6 Quality Assurance

Availability:
The user base will potentially include students and instructors at remote locations such as Paris. By placing the ICTM on the internet, students and instructors can explore and modify web pages contained at the site.

Performance:
The translation of a web page will be done as soon as the page is updated. The search will query and return results within 10 seconds.

Usability:
Non-experienced instructors can enter the instructional site and make use of all the available functionality in order to modify the student site. The user interface is uncomplicated and intuitive enough for any user to understand. The bulletin board feature, on both user and instructor sites, is simply a text message box with a button to submit and post the message to the proper bulletin board.

Reliability:
Backup copies of the student web pages can be maintained by the UCS in the event of data loss.

For a more detailed quality assurance analysis, please refer to Section 6.0 of the System and Software Requirements.

4.7 Facilities and Related Concerns

5.0 Resources

5.1 Work Breakdown Structure

The hierarchical structure of the system is Figure 5.1. This show the structure of the subsystems and activities associated with the ICTM. The activities and system contents of the ICTM include the Plans and Requirements, Product Design, First Increment, and Second Increment. First increment is for essential capabilities and second increment is for desirable capabilities. Each Increment contains Detailed Design, Coding, Unit test, and Integration and test. Optional capabilities will be developed future.

Figure 5.1 Work Breakdown Structure

Because a team of five graduate students enrolled in CS577b will be assigned to develop this system, the cost is essentially zero and the budget need not reflect this.

However, at this point, a server to house the ICTM system as well as an adequate translation provider has not been found which could potentially affect and impact the budget of the ICTM system.

In order to ensure performance standards set by the SSRD, a server with at least 10 gigabytes of hard disk space will be needed to house the ICTM and any archived material. The server should have a fast processor and should cost anywhere from $3000 to $10000.

The monthly service cost or the cost of purchasing a COTS translation software package is unknown. But we will allocate approximately $1000 for the purchase of a COTS translation software package in case a free, on-line translation provider is not found.

For further details please refer to the Development Cost Analysis of the Feasibility Rationale (Section 3.1.1)

6.0 Assumptions

Following some conditions must be maintained in order to implement the plans abolve within the resources specified. If one or more of these assumptions becomes invalid, the plan should be renegotiated.

First, each software module should provide system integrity and no code should have the possibility of volatility.

Second, not noly the ICTM but also applications including COTS should be delivered on development schedule.

Third, continuous funding for system maintaining should be supported.

Finally, the new developers who will develop the optional capabilities should be familiar with the ICTM, the componests, and all of additional applications.

7.0 Glossary

Authentication: The verification of the identity of a person or process. In our proposed system, authentication verifies that a user is a registered instructor and/or student.

Authoring web pages: The modification of a web page. In our ICTM system, the editing operations that an instructor can choose from are adding and deleting links and images. The authoring of a web page typically consists of creating an HTML file and editing it directly by hand. Our system will shield the instructor user from having to know HTML, will create HTML files, and allow the addition/deletion v of links and images by merely clicking on a few buttons and entering some simple commands.

Bulletin Board: In reference to a physical piece of board on which people can pin messages written on paper for general consumption - a "physical bboard"), a bulletin board is a computer and associated software which typically provides an electronic message database where people can log in and leave messages. Any registered user may submit or read any message in these public areas.

Dummy page: a Java applet that duals as a page preview source as well as the area in which an instructor user can perform various web authoring commands such as text manipulation, link/video addition, and link/video deletion.

FTP: Stands for file transfer protocol. This command is used to retrieve files from remote sites.

GIF: Graphics Interchange Format: A standard for compressed digitized images.

GUI: Graphical User Interface: The use of pictures rather than just words to represent the input and output of a program. A program with a GUI runs under some windowing system (e.g. The X Window System, Microsoft Windows, Acorn RISC OS, NEXTSTEP). The program displays certain icons, buttons, dialogue boxes etc. in its windows on the screen and the user controls it mainly by moving a pointer on the screen (typically controlled by a mouse) and selecting certain objects by pressing buttons on the mouse while the pointer is pointing at them.

HTML: Stands for Hypertext Markup Language. A Hypertext document format used on the World-Wide Web. Built on top of SGML. "Tags" are embedded in the text. A tag consists of a "<", a "directive" (case insensitive), zero or more parameters and a ">". Matched pairs of directives, like "" are used to delimit text which is to appear in a special place or style.

ICTM: The International Cross-Cultural Teaching Model

Instructional site or Student Site: A web site that is comprised of a student web page, a student bulletin board, a search feature, an instructor form emailer, and a link to the instructor site.

Instructor : A user who has the authorization to access the both the student and instructor site.

Instructor site: A web site that is comprised of an instructor bulletin board, a dummy page, a web page creation button, web page authoring tools, a web page selection feature, and a fetch button. This site can only be accessed by authorized instructor users.

Java: A simple, object-oriented, robust, secure, portable, architecture-neutral, general-purpose programming language developed by Sun Microsystems. Java supports programming for the internet in the form of platform-independent Java "applets"

JPEG: Joint Photographic Experts Group: Standard image compression algorithm that is designed for compressing either full-color or grey-scale digital images of "natural", real-world scenes.

Perl: Practical Extraction and Report Language General purpose language, often used for scanning text and printing formatted reports. It provides extensive support for regular expression matching, dynamically scoped variables and functions, extensible run-time libraries, exception handling and packages, provide/require.

Student : A user who has the authorization to access the student site but not the instructor site.

Student assistant: A work-study student who has been hired by an instructor to oversee the development and maintenance of the current system. The student assistant will in all likelihood, play the role of the system administrator of the ICTM.

Student site or Instructional Site: A web site that is comprised of a student web page, a student bulletin board, a search feature, an instructor form emailer, and a link to the instructor site.

System administrator or system maintainer: Person responsible for ICTM account creation and maintenance as well as day-to-day maintenance of the site (backups, file deletion, etc.)

Translator: In the context of our project, a translator is a computerized software module that translates words or phrases from one linguistic language (English/French) to another.

User: An authorized student or instructor.

Web page authoring: Web page editing (text manipulation, link/image addition, link/image deletion, etc.)