Make your own free website on Tripod.com

Review Website:

Mark Stevens


Homework 1a

Overview

Spiral Model

Background material:

Major tasks( repeated as necessary) such as:

Strengths:

Weaknesses:

Appropriate domain:

Inappropriate domain:

 

Prototyping Model

Background Material:

Representation of components and relationship:

Goes through 3 circular steps:

Appropriate domain:

Inappropriate domain:

Comparison of the Spiral and Prototyping Model:

Questions anc Comments

  1. What are the relationships and rules that need to be considered when using the spiral and prototyping model?
  2. What are the related tools and methodologies related to both the models?
  3. What are others domain besides the ones listed above?
  4. How is the model represented in diagrams? I think it should be clearer if there are diagrams to illustrate the components and relationship.

Homework 2

Overview

Background material and information:

It is a distributed model.

Relationship to Lifecycle Models:

Spiral Model

Advantage:

Disadvantage:

Prototyping Model

Appropriate uses:

Inappropriate uses:

Questions and Comments:

  1. Why and in what area that the spiral model ideal for networking systems? Why is this point considered as an advantage to the client/server architecture?
  2. I agree that spiral model does have high risk assessment which increase reliability but does a client/server necessary to be associated with high risk? If yes, why?
  3. What makes client/server better than other software architecture?

Homework 4

Overview

Data Flow Diagrams (DFDs)

Data Flow Diagrams are diagrams that show the flow of data through a system.

Representation of component:

There are four types of components:

Relationship and Rules:

Strengths:

Weaknesses:

Appropriate domain:

Inappropriate domain:

Tools:

SADT

It is designed to handle more complex method.

Representation of Components:

Can be broken down into two sections

Each diagram has four major activities.

The functions are broken into subfunctions.

Strengths:

Weakness:

Appropriate domain:

Inappropriate domain:

Tools:

Questions and Comments


Project 1

Overview

Problem Statement:

This project is about the software which enables the user to keep track of the inventory items in stock and resulted from sales, to update stock records and to project the softwares to purchase.

Current System:

Physical:

The current system consists of manually logging :

  1. Customer ID number
  2. Title and serial number of the software purchased
  3. Date purchased
  4. Customer's signature

Into a three-ring binder at the time of purchase.

Logical:

  1. Ringing the customer's purchase
  2. Completing logbook entry.

Proposed System:

Physical:

The proposed system consists of

  1. Scanning purchased item
  2. Entering customer information

Logical:

  1. Subtracting the purchased item from the current inventory.
  2. Adding the purchased into the sales inventory.
  3. Verify customer's ID.
  4. User update inventory.

Questions and Comments

  1. Since the project needs scanning, don't you think that in the hardware required, a scanner should be added as a requirement?
  2. How about securities features in the system?
  3. Why not include the logbook idea in the current logical system into the proposed logical system? That certainly will make maintenance easier and more organized.

Project 3

Overview

Microsoft Project 98 vs. Open Plan Professional:

This project is about the comparison and contrast of Microsoft project 98 and Open Plan Professional.

The areas that the group compares and contrasts are

 

Questions and Comments

  1. What features make Microsoft Project 98 more outstanding and user friendly that other software management tools?
  2. Can you identify which type of projects is more suitable to use Microsoft Project 98 rather than Open Plan professional?