0% found this document useful (0 votes)
18 views12 pages

Scope Document Updated Template

This document is a project proposal scope document for a Bachelor of Science in Computer Science at COMSATS University Islamabad, detailing the project's objectives, problem statement, proposed solutions, and methodologies. It includes sections on related systems, project advantages, scope, modules, limitations, tools, and team responsibilities. The document serves as a comprehensive guide for the project's development and evaluation process.

Uploaded by

Noman Haider
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views12 pages

Scope Document Updated Template

This document is a project proposal scope document for a Bachelor of Science in Computer Science at COMSATS University Islamabad, detailing the project's objectives, problem statement, proposed solutions, and methodologies. It includes sections on related systems, project advantages, scope, modules, limitations, tools, and team responsibilities. The document serves as a comprehensive guide for the project's development and evaluation process.

Uploaded by

Noman Haider
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

COMSATS University Islamabad, Vehari Campus

Project Proposal
(SCOPE DOCUMENT)

for

PROJECT NAME
Version 1.0

By
Student Name 1 CIIT/SP09-BCS-xxx/ISB

Student Name 2 CIIT/SP09-BCS-xxx/ISB

Supervisor
Supervisor Name

Bachelor of Science in Computer Science (20xx-20xx)


SCOPE DOCUMENT REVSION HISTORY

No. Comment Action

Supervisor Signature:__________________

Date:_____________

Table of Content
s

Abstract.....................................................................................................................................ii

1. Introduction......................................................................................................................1

2. Problem Statement...........................................................................................................1

3. Problem Solution for Proposed System.........................................................................1

4. Related System Analysis/Literature Review..................................................................1

5. Advantages/Benefits of Proposed System......................................................................1

6. Scope..................................................................................................................................2

7. Modules.............................................................................................................................2

8. System Limitations/Constraints......................................................................................2

9. Software Process Methodology.......................................................................................2

10. Tools and Technologies................................................................................................3

11. Project Stakeholders and Roles..................................................................................3

12. Team Members Individual Tasks/Work Division.....................................................4

13. Data Gathering Approach...........................................................................................4

14. Concepts........................................................................................................................4

15. Gantt chart....................................................................................................................4

16. Mockups........................................................................................................................5

17. Conclusion.....................................................................................................................6

References.................................................................................................................................7

Plagiarism Report....................................................................................................................7

i
Project Category: (Select all the major domains of proposed project)

A-Desktop Application/Information System B-Web Application/Web Application based Information System


C- Problem Solving and Artificial Intelligence D-Simulation and Modeling E- Smartphone Application F-
Smartphone Game G- Networks H- Image Processing Other (specify category)

Abstract

Provide a one to two paragraph summary of your project. The abstract should give an idea of what
your project is trying to achieve. Think of your abstract as a condensed version of your whole project.
By reading it, the reader should understand the nature of your project. It should be comprehensive,
and concise.

ii
1. Introduction
Specify the purpose of this project proposal document along with description detailed
background of the system. (Usually in 10-12 sentences).

2. Problem Statement
What problem does your software solve? Why you are developing this system? Does the
same system already exist? If yes, how will a re-implementation aid your learning? What
skills do you expect to learn from this project? (Usually in 14-16 sentences)

3. Problem Solution for Proposed System


Briefly explain how your system solves the problems mentioned in the problem statement.
(Usually in 14-16 sentences)

4. Related System Analysis/Literature Review


Write about the existing/similar systems related to your proposed project. At least three
existing systems should be discussed.
Don’t use more than 4 sentences for explaining a single system/application.
Briefly explain the related system analysis which help to specify the contribution of the
proposed project.
(Note: Research based projects may provide literature review instead of related system
analysis.)

Table 1: Related System Analysis with proposed project solution

Application Name Weakness Proposed Project Solution


The name of related Weaknesses may include The way the proposed project
application(s). limited features, low mitigates the weaknesses.
quality
functionality and
processes.

5. Advantages/Benefits of Proposed System


Write down the advantages and benefits of the system you are developing. In other words,
you have to mention here advantage of your proposed solution to the existing problem.
1
(Usually in 5-7 advantages)

6. Scope
Write down the scope of your project in a paragraph. Briefly define the main functionalities
of the proposed project. Scope defines the boundaries and range of the proposed solution, that
what would be the part of your project and what will be not. Write down in logical flow with
consistency. (Usually in 14-18sentences)

7. Modules
Write down the modules of the proposed project. Don’t forget to mention special/new
features.
Briefly explain your one module in 6 to 8 sentences.
(Note: Usually 5-6 Modules for 2 student’s projects and 8-9 modules for 3 student’s project)

Explanation of a Module: Module is a section of a program that performs a task. Programs


consist of modules, each of which contains one or more routines. The term routine is
synonymous with procedure, function, and subroutine.
Example:
Enterprise resource planning (ERP) software - is comprised of several large modules (for
example, finance, supply chain and payroll, etc.), which may be implemented with little or no
customization.
(Briefly explain each module with respect to major functionality in user context)

Module 1: Module Name Module 2: Module Name

8. System Limitations/Constraints
Write down the limitations and constraints of the proposed project. (Usually 2-4 constraints)

9. Software Process Methodology


Write down your software methodology/ software process that will be used for
project development. .Also mention why you have chosen this methodology. (Usually 3-5
sentences)
1) You can use Object Oriented Methodology, or Procedural methodology.

2
2) Choice of methodology will affect choice of tools and technologies
3) Choice of methodology will affect nature of design (SDS)
4) Choice should be made depending on your expertise and your needs e.g. most
simulation and device level software can only be programmed in procedural
languages.

3
10. Tools and Technologies
Mention all the hardware/software tools and technologies with version number which will be
used in implementation of the project. Write about the APIs, language(s), SDK(s) etc. which
you will use for implementation.
Example:

Table 2: Tools and Technologies for Proposed Project

Tools Version Rationale


MS Visual Studio 2015 IDE
MS SQL Server 2015 DBMS
Tools And Adobe Photoshop CSC 6 Design Work
Technologies MS Word 2015 Documentation
MS Power Point 2015 Presentation
Pencil 2.0.5 Mockups Creation
Technology Version Rationale
C# 6.0 Programming language
SQL 2013 Query Language
Html 5 Web Development

11. Project Stakeholders and Roles


Write down the project stakeholders and their roles.

Table 3: Project Stakeholders for Proposed Project

Project Sponsor All web applications and desktop applications should have real client.
Mention your project sponsor.
Default option will be: COMSATS University, Islamabad
Stakeholder Mention your stake holders with their roles and responsibilities. Default
option will be:
 Students names
 Project Supervisor Name: Mr./Miss …
4
 Final Year Project Committee: Evaluation of project

12. Team Members Individual Tasks/Work Division

Table 4: Team Member Work Division for Proposed Project

Student Name Student Registration Number Responsibility/ Modules


Student 1 Name Student 1 Registration Number Describe the work division of each
student along with modules
E.g.
Mr. Ali (Module1-Module3) Augmented
reality and Databases tasks.

13. Data Gathering Approach


Write down information and requirement gathering approaches for proposed project e.g.
Interview, Questionnaire etc. (Usually 3-5 sentences)

14. Concepts
Mention the concepts that you will learn while doing the proposed project.
For example: Augmented Reality, Virtual Reality, Algorithms, API’’s Code injection,
Closures,
VI technique etc.
Not more than 4 sentences for one concept. (Usually 3-5 concepts are briefly mentioned)
Example:
Concept-1: Concept Name E.g., Augmented Reality (Briefly give the overview of concept
with respect to your project)

15. Gantt chart


Create the Grant Chart and provide estimated start and end dates of all proposed
modules/tasks for each team member. Also identify the dependencies (which tasks cannot be
started/completed, until the dependent task is completed). Gantt chart can be created using
MS Project.

5
Figure 1: Gantt Chart

16. Mockups
Insert minimum mockups (Usually 4-6 mockups) which show the major modules mentioned
in the scope section of the document. Do not include mockups for Login, Signup, Forgot
Password, Contact Us, About Us etc. If the project is a Web or a Smartphone Application,
then include at- least three mockups from each part of the project. You can design mockup in
any design tool for example pencil tool ([Link] or Balsamiq
([Link]

6
17. Conclusion
Conclude this document. (Usually 4-5 sentences)

7
References
Use IEEE reference style.
Mention the books, research papers, web links etc.

Plagiarism Report
Attach the Plagiarism report of your project scope document from library staff of turnitin tool
([Link]

Common questions

Powered by AI

Defining the scope in software project development is critical as it sets the boundaries and expectations for what the project will achieve. A well-defined scope facilitates accurate planning, resource allocation, and risk management . Poorly defined scope can lead to scope creep, which is the expansion of project requirements without corresponding adjustments to time, cost, and resources . This can result in unfinished or low-quality deliverables and increased project failure risk .

The common system limitations and constraints identified for software project development include resource availability, technological capabilities, budget constraints, and time limitations . These constraints affect project outcomes by limiting the scope of what can be achieved within the given parameters. They necessitate careful prioritization of features and may lead to trade-offs in functionality or quality . Effective planning and management are required to mitigate these constraints and achieve desired project outcomes.

Tools and technologies selected for a software project impact its development process by determining the platforms and frameworks available for use, affecting programming efficiency, compatibility, and project scalability. For example, choosing a robust IDE like MS Visual Studio can enhance productivity with advanced debugging and testing features . The selection of appropriate databases or APIs influences system performance and flexibility, impacting the final outcome in terms of stability, user experience, and ability to meet project goals .

Mockup creation contributes to the design and validation process by providing a visual representation of the system, allowing stakeholders to visualize and approve user interfaces and workflows early in the development cycle. This can highlight usability issues and guide developers in making necessary adjustments before actual coding begins . However, mockups have limitations as they do not reflect backend functionality or actual data processing capabilities, and overly detailed mockups can misrepresent system capabilities if not carefully managed .

The data gathering approach impacts the quality and relevance of requirements for a software development project by determining the accuracy and completeness of the information collected. Methods like interviews and questionnaires can provide detailed insights into user needs and expectations . Effective data collection ensures that the project requirements are based on actual user and stakeholder input, thereby increasing the likelihood of developing a solution that aligns with end-user needs and minimizes misinterpretations .

Existing systems analysis and literature review contribute to the formulation of a proposed project's objectives by identifying gaps and weaknesses in current solutions and methodologies . This information helps define unique features and improvements that the proposed project can offer. Furthermore, by understanding similar systems, developers can borrow successful elements and avoid known pitfalls, allowing for a more targeted and efficient design process .

Project stakeholders and their roles influence the success and direction of a software development project by determining the requirements, resources, and guidance needed to achieve project goals. Stakeholders such as sponsors, supervisors, and team members bring different perspectives and expertise, enabling comprehensive planning and decision-making . Their involvement can dictate project priorities, risk management strategies, and can provide crucial support for overcoming obstacles .

The choice of software process methodology influences the design and implementation of a software project by dictating the frameworks and practices used throughout the project lifecycle. For instance, an Object Oriented Methodology allows for modular design and reuse of components, while a Procedural Methodology might be more suitable for linear, process-driven tasks . This choice impacts how tools and technologies are selected and how the system is architected, affecting the flexibility, scalability, and maintainability of the final product .

The proposed benefits of a new software system over existing alternatives include enhanced functionality, improved user experience, and better performance efficiency . These benefits align with user needs by addressing specific shortcomings in current systems, such as lack of features or poor usability, thereby offering a more comprehensive solution that meets both basic and advanced user requirements .

The design of modules in a software project enhances functionality and ease of maintenance by compartmentalizing different functions into discrete sections, allowing for focused development and testing processes. This modular design supports reusability and substitution of components with minimal impact on the overall system, facilitating updates and integration of new features . For instance, defining separate modules for distinct functions like user authentication, data processing, and reporting, aids in isolating and fixing issues within specific domains without affecting others .

You might also like