Scribd
Upload
7 views

Assignment 1 Final

This document outlines the assignment requirements for a Software Engineering course at the University of Management and Technology, detailing submission guidelines, project structure, and evaluation criteria. It emphasizes the importance of originality, proper formatting, and clear project descriptions, including objectives, scope, and target users. Additionally, it includes specific questions and sections to guide students in developing their project proposals.

Uploaded by

noobscaferen
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views

Assignment 1 Final

This document outlines the assignment requirements for a Software Engineering course at the University of Management and Technology, detailing submission guidelines, project structure, and evaluation criteria. It emphasizes the importance of originality, proper formatting, and clear project descriptions, including objectives, scope, and target users. Additionally, it includes specific questions and sections to guide students in developing their project proposals.

Uploaded by

noobscaferen
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Department of Computer Science

University of Management and Technology

Assignment Description File


Course Name: Software Engineering
Section:
Teacher: Noor Fatima
Student Name & ID:
Assignment No.: 1
Deadline: Late submissions not Accepted
Follow LMS submission deadline

NOTE: PLAGIARISED ASSIGNMENT EITHER FROM CLASSMATES OR INTERNET WILL BE


MARKED STRAIGHT ZERO.NO ASSIGNMENT WILL BE ACCEPTED AFTER DEADLINE. ALWAYS
METION SECTION ON YOUR ASSIGNMENT OTHERWISE MARKS WILL BE DEDUCTED. USE THE
SAME TITLE PAGE AS ASSIGNMENT DESCRIPTION

USE THIS FORMAT TO SUBMIT YOUR SOLUTIONS.

1) Project Title

2) Name and ID of Student

3) Project Advisor (Name, Email Address)

4) External Collaboration/Funding (if any) + Paid or Unpaid (Confirmed or Expected)


5) Project Description (Brief Introduction) The introduction part should include:
• Overview of topic/domain
• Description of project/problem (Explain what it is about the problem that makes it an
interesting / worthwhile idea for a project)
• Describe the solution you plan to explore
• Expected results/product

6) Major Features/Requirements/Objectives (Tentative)


The objectives of the project must reflect with the project description generated earlier. The
objectives must be clear, measurable and achievable.

• For a project that involves designing and developing a system:


Give an outline of the functional and non-functional requirements of the system

• For a project that involves conducting a practical investigation:


Give an outline of the questions your investigation will seek to answer and how the
software you will develop will be used to prove or validate your investigation outcomes.

7) Scope of the Project/Proposed System


This section describes the boundaries of the project. Basically, what does the project cover?
Make sure each task is described in sufficient detail so we can understand what you will do.

8) Target Users/Beneficiaries of the Proposed System


This section should list down the target users of the proposed system.In this section, you should
discuss the importance of the project to users, organizations or society.

9) Tools/Technologies (Tentative Listing)


State what methods and/or tools you will need to use. What kind of hardware / software will you
be using during development?

Assignment part 2

Q1: Give complete introduction about your project introduction should include (project
overview, problem statement, customer, affected groups, assumptions, dependencies/external
systems, goals)

Q2: Mention all the stakeholders of your project

Q3: Also tell how they are stakeholders of project

Q4: Do domain analysis of your project


SEE THE TEMPLATE ATTACHED
This section should describe the project and the software product being to be built. No text is necessary between the
heading above and the heading below unless otherwise desired.

1.1 Project Overview


Give a short summary of the project objective and the system to be analyzed
Functional specifications are a description of needs or desires for a product. Identify and document what is really
needed, in a form that clearly communicates to the client and to development team members. Define the
requirements unambiguously, so that the risks are identified and there are no surprises when the product is finally
delivered.
Following are the sample artifacts for this section:
 Problems or Overview Statement
 Customer
 Goals
 System functions
 System attributes

1.2 Problem Statement


The purpose of this project is to …
The problem statement should be brief, comprising of no more than 50 words

1.3 Customer
A brief description of the client. The organization, its products/services etc.
e.g.
Company X offers solutions for companies who want to establish a portal on the Trading Net and those who want to
host portals for others. Company X was founded in 1992 and went public in 1998.

1.4 Affected Groups


Those impacted by the deployment of the system. This can be a simple list as well as a bulleted one with short
explanations. e.g.
 Sales staff
 Cashiers
This may include users as well as support groups

1.5 Assumptions
Things we assume will be true.
e.g.:
 We will receive all necessary technical support from the engineers at cMeRun, Select and Mellon Bank to
help design the interfaces between their systems and enGyro.
 All database maintenance will be handled by the client.
 There will be no real-time interfacing with any accounting systems.

1.6 Dependencies/ External Systems


Systems and/ or products, this project depends upon for its completion.
e.g.
 Cyber Cash

1.7 Definitions and Acronyms


Provide definitions or references to all the definitions of the special terms and acronyms used within this document.

1.8 Reference/ Source Documents


Provide references to all documents that have been consulted during the analysis phase.

1.9 Goals
This brief section should focus on what the client wants to achieve. It must enumerate the objectives of the top
management and what it hopes to accomplish from the proposed system.

You might also like