Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Assignment 1 on Software Engineering - Spring 2007 | CSE 112, Assignments of Software Engineering

Material Type: Assignment; Professor: Krueger; Class: Software Engineerng; Subject: Computer Science & Engineering; University: University of California - San Diego; Term: Spring 2007;

Typology: Assignments

2009/2010

Uploaded on 03/28/2010

koofers-user-1ax
koofers-user-1ax 🇺🇸

10 documents

1 / 2

Toggle sidebar

Related documents


Partial preview of the text

Download Assignment 1 on Software Engineering - Spring 2007 | CSE 112 and more Assignments Software Engineering in PDF only on Docsity! Ingolf H. Krueger CSE 112 Spring 2007 Homework #1 Due April 26, 2007, in class Please answer the following questions using lucid, concise English language; use the electronic word processing system and graphics tools of your choice to produce high- quality output. At the due date, please turn in stapled hardcopies of your work, as well as an electronic copy via email to the TA. Scores for late assignments will be multiplied by 0.8 for each day late. Please remember that this is an individual assignment; refer to the class web pages for the definition of “individual”. Please find a short list of open source tools for creating graphs etc. at HTUhttp://java- source.net/open-source/uml-modelingUTH; others are easy to locate via Google and other search engines. Consider the following description in the context of projects and project management: (i) A project has a title, an expected start date, and an expected end-date. The life- cycle of a project consists of the following phases: application, under review, in execution, terminated. Projects that are in execution have a start-date, and an expected end-date; they consist of a sequence of iterations – each iteration has its defined start- and end-date, as well as an actual start- and end-date. (ii) Each project has a list of tasks that need to be completed. Each task can be in one of the following states: not started, started, and completed. Each iteration is associated with a subset of the overall task list; this is the set of tasks that is being worked on in that iteration. (iii) A project manager has access to multiple resources, ranging from personnel to equipment. Resources are assigned to projects. Each resource has certain properties depending on its type; examples are “ideal work days” (for personnel) and number and location (for equipment). Each resource can be associated with a project for a certain duration and percentage. For personnel, for instance, that reduces the number of available “ideal work days” by the indicated percentage. (iv) Each project also maintains a list of risks. Each risk has a unique number, a short header, a description, a probability and a likelihood (low, med, high), and a mitigation strategy. Assume that your goal is to develop a web-based project management application based on the analysis above. The customer wants a three-tiered solution, consisting of a presentation layer, application layer, and a data layer. The core features of the applications should include • Add/delete/modify user accounts • Add/delete/modify projects, tasks, resources, … • Associate entities with one another • Monthly billing • File upload/download for files related to projects 1/2
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved