Skip to content Skip to navigation

Connexions

You are here: Home » Content » Assignment

Navigation

Lenses

What is a lens?

Definition of a lens

Lenses

A lens is a custom view of the content in the repository. You can think of it as a fancy kind of list that will let you see content through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual member, a community, or a respected organization.

What are tags? tag icon

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

This content is ...

Affiliated with (What does "Affiliated with" mean?)

This content is either by members of the organizations listed or about topics related to the organizations listed. Click each link to see a list of all content affiliated with the organization.
  • VOCW

    This module is included inLens: Vietnam OpenCourseWare's Lens
    By: Vietnam OpenCourseWare

    Click the "VOCW" link to see all content affiliated with them.

Recently Viewed

This feature requires Javascript to be enabled.
 

Assignment

Module by: Hung Vo. E-mail the author

Summary: This is the assignment for the Software Engineering course.

Assignment 1. Project Feasibility Study and Plan

Write a short feasibility report that describes the project that you have selected. The exact form of the report is up to you, but it should be well written and suitable to present to an external client. The length is likely to be between five and ten pages.

The report should include the following:

  • The client for whom the work will be done.
  • Visibility plan. How will you keep in contact with the client and report progress? How will you communicate among your team?
  • A statement of the task to be undertaken.
  • A preliminary requirements analysis.
  • Suggested deliverables.
  • Process to be followed, e.g., modified waterfall model, iterative refinement, prototype, phased development, etc.
  • Outline plan, showing principal activities and milestones.
  • Discussion of business considerations.
  • Risk analysis. What can go wrong? What is your fallback plan?
  • Probable technical requirements

This report is a group assignment. All members of the project team should share in the production of the report.

Assignment 2. Progress Report and Presentation

During the semester each team will give three presentations with associated reports on the work completed. You will make a 45 minute presentation to the client, the Instructor and the Teaching Assistant assigned to your project. Everybody is expected to be a presenter at least once.

The first progress report and presentation should complete one third of the total work from the feasibility study.

If you are following an iterative process the first progress report should mark a major milestone when you can report visible progress to your client. Typically, this will include a first set of requirements, a provisional design and a prototype that can be used to demonstrate the functionality of the system, including user interface design.

If you are following a modified waterfall development process, this progress report should include completion of the requirements phase. Carry out the requirements analysis, definition and specification for your project. Write a requirements document. The exact form of the document is up to you, but it should be well written and suitable to present to your client. In writing a requirements report, pay particular attention to the following:

  • The report must be understandable by the client.
  • The requirements must be specified in sufficient detail to test against the implementation.
  • The requirements must be the client's, not your own concepts.
  • Design concepts must be clearly separated from requirements.
  • Requirements should be partitioned into those that must be met by the first release and those that are optional.

Assignment 3. Progress Report and Presentation

The second presentation and report will follow the same format as the first. You will make a 45 minute presentation to the client, the Instructor and the Teaching Assistant assigned to your project. Remember that everybody is expected to be a presenter at least once during the semester.

The second progress report and presentation should complete two thirds of the total work from the feasibility study.

If you are following an iterative process this progress report should mark a major milestone when you can report visible progress to your client.

If you are following a modified waterfall process, this progress report will be the completion of the design phase. You should probably have already begun implementation.

The exact form of the report is up to you, but it should be well written and suitable to present to your client. In writing a design report, pay particular attention to the following:

  • The report must be understandable by the client.
  • The design should include both system and program design.
  • Design concepts must be clearly separated from requirements and the implementation.
  • Update your schedule to confirm that you will have an operational system by the end of the semester.

Assignment 4. Final Presentation

The final presentation and report will follow the same format as the others. You will make a 45 minute presentation to the client, the Instructor and the Teaching Assistant assigned to your project. Remember that everybody is expected to be a presenter at least once during the semester.

This presentation should describe to the client and the course team what has been accomplished during the semester and should include a demonstration of your system in operation. The documentation should be a complete hand-over package, which has been entered into your project management system, so that the client's staff can put your project into production, extend and maintain it.

Assignment grading rubric

Table 1
Content & Criteria Points Possible Points Obtained Comments
Feasibility and Planning 10    
  What is the scope of the proposed project? 2    
  Is the project technically feasible? 2    
  What are the projected benefits? 2    
  What are the costs, timetable? 2    
  Project Risk Identification? 2    
Requirements 10    
  Requirements identification 2    
  Requirements analysis 2    
  Requirements definition 2    
  Requirements specification 2    
  Requirements report 2    
System and Software Design 20    
  Design describes the system from the software developers' viewpoint 5    
  System design: Match the requirements to hardware or software systems. Establishes an overall system architecture 5    
  Program design: Represent the software system functions in a form that can be transformed into one or more executable programs 5    
  Tools: apply tools for designing 5    
Implementation and Testing 10    
  Is the level of language that the program offers clearly indicated? 1    
  Is it easy to start the program? 1    
  Is the user interface easy to understand? (For example, is the screen layout clear and easy to interpret?) 2    
  Does the program include scoring? 2    
  Individual components are tested against specifications. 2    
  The individual program units are integrated and tested against the design by the students as a complete system. 1    
  The complete system is tested against the requirements by the client. 1    
Maintenance 10    
  Operation: The system is put into practical use. 2.5    
  Maintenance: Errors and problems are identified and fixed. 2.5    
  Evolution: The system evolves over time as requirements change, to add new functions or adapt the technical environment. 2.5    
  Phase out: The system is withdrawn from service. 2.5    
Quality of software 10    
  Maintainability- easy to maintain to meet changing needs 2.5    
  Dependability- reliability, security, safety 2.5    
  Efficiency- not wasting system resources 2.5    
  Usability- user friendly, good documentation 2.5    
Performance of each student’s effort in the project 10    
  Student had a major role in the success of the project 2    
  Student always showed up on time for project meetings 2    
  Student completed his/her part of the project. 2    
  Student showed a lot of interest in the project 2    
  Student played a major role in the project design, implementation and validation 2    
Report 10    
  Overview/introduction 2    
  Organization of body 2    
  Quality of result 2    
  Effective data presentation 2    
  Conclusion 2    
Oral presentation 10    
  Organization (presentation refined and clearly explained, information logically introduced and explained, the area of study's connection to the broad topic and the group's work is clearly explained) 2    
  Content (presentation reveals good use of sources, provides pertinent information) 2    
  Presentation (speaks clearly, uses appropriate language, uses appropriate body language, meets time specifications) 2    
  Questions 4    

Content actions

Download module as:

PDF | More downloads ...

Add module to:

My Favorites (?)

'My Favorites' is a special kind of lens which you can use to bookmark modules and collections. 'My Favorites' can only be seen by you, and collections saved in 'My Favorites' can remember the last module you were on. You need an account to use 'My Favorites'.

| A lens I own (?)

Definition of a lens

Lenses

A lens is a custom view of the content in the repository. You can think of it as a fancy kind of list that will let you see content through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual member, a community, or a respected organization.

What are tags? tag icon

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

| External bookmarks