The document outlines a software engineering project for students, where teams must develop a solution addressing real-life problems. It describes project requirements, team roles, expected functionalities, including user interactions and challenges such as budgeting and risk analysis. The primary goal is to create an application aiding students preparing for admission tests by connecting them with local assistance and accommodations.

1. Page | 1
AIUB | FSIT
SE PROJECT
SOFTWARE ENGINEERING | FALL 2019 - 2020
What to make?
Each team is required to come up with an idea (either Category A or Category B), make a plan and
submit. It can be either purely software or a combination of software and hardware. You must choose at
least one of the options for technology, but if any team is optimistic enough: can choose all of the
available options.
How is a team made?
A team is up to four students. In addition to each team, other people are allowed to help. A team can
have a mentor, who advises on the project. A team can also have associates, who must be eligible
students that can help the team with things, with business model planning, marketing, and so on. These
people are not members of the team as such but it's good to have help sometimes.
Problem domain
Category A: Find a real-life problem, even in your own life or community, and then work to solve it.
Build a project that could change lives. The next big thing could come from you. Facebook and Twitter
started as student projects. Your ideas could be next. Come up with an innovative application idea and
proceed accordingly.
OR
Category B: There might be dozens of software to solve our real-life problems and provide
benefit to business. Come up with an idea that will extend the current version of those software.
Technology
Name: Rokon Md Shafaat Jamil ID: 17-33084-1 Section: E
Project name: Help For Admission Test Students
CO4: Explain the roles and their responsibilities in the software project management
activities
Background
information and project
goals (5)
Project management (5) Taking
responsibility (5)
Spelling and
grammar (5)
Total
(20)

2. Page | 2
Option A: Web
Option B: Desktop
Option C: Mobile Phones/Handheld devices
Project:Help for AdmissionTest Students
Table of Contents Page No.
Conceptual Foundation .................................................................................................................3
Does the project have a clear target market or audience? ..........................................................3
Does the team demonstrate a thorough understanding of the need, problem or opportunity,
including evidence of research into the need, problem or opportunity? .........................................3
Is the project’s purpose and basic functionality easily understood? ………………………. 3
UML ...............................................................................................................................................4
Use Case ......................................................................................................................................4
Activity Diagram .........................................................................................................................5
Class Diagram ……………………………………………………………………………… 6
Effort Estimation ...........................................................................................................................7
Budgeting .......................................................................................................................................8
Scheduling.......................................................................................................................................8
Risk Analysis ............................................................................................................................... 9

3. Page | 3
ConceptualFoundation
Does the project have a clear target market or audience?
Answer: Yes,thisprojecthasa cleartargetmarketor audience.The targetaudience are the
studentswhocome foradmissiontestandalsothe studentswhowill lookforaplace to stay
afterthe admissiontest.
Does the team demonstrate a thorough understanding of
the need, problem or opportunity,includingevidence of
research into the need, problem or opportunity?
Answer: yes,itisunderstoodbythe team, forexample if astudentcomestoa new citywith
little tonoknowledge of the surroundingsof the cityandthe examvenue.Thenitwill aproblem
for him/her.Instatistics,itisfoundthatabout70% of the studentswhocome for admissiontest
are cluelessof where tostaybefore orafterthe exam.About80% donot know about the exam
venue.So,itisclearthat HATS the studentswhoare in desperate needof helpwillbe aided
witha secure guidance universitystudentandvertical local people of thatspecificarea.
Is the project’s purpose and basic functionalityeasily
understood?
Answer:yes,the project’spurpose andbasicfunctionalityeasilyunderstood.
Two types of user in this system:
 Studentsinneedof help
 People whoare helping
Functionalities ofthis project:
 Helppostwill be posted
 Assistorwill helphim/her
 Will provide aplace to stay
 Will take to examvenue andreturnaswell
 Will stayas payingguestif necessary
 Paymentcanbe paidinadvance by bkash/debitcardorin cash onmeeting

4. Page | 4
UML
UML is an acronymthat standsfor UnifiedModelingLanguage.Simplyput,UML is a modern approach
to modelinganddocumentingsoftware.Itisbasedondiagrammaticrepresentationsof software
components.Asthe oldproverbsays:“a picture iswortha thousandwords”.Byusingvisual
representations,we are able tobetterunderstandpossible flawsorerrorsinsoftware or business
processes.Mainly,UML hasbeenusedas a general-purpose modelinglanguage inthe fieldof software
engineering.
Use Case:
A use case diagram isa dynamicor behaviordiagraminUML. Use case diagramsmodel the functionality
of a systemusingactorsand use cases.Use casesare a setof actions,services,andfunctionsthatthe
systemneedstoperform.Inthiscontext,a"system"issomethingbeingdevelopedoroperated,suchas
a website.The "actors" are people or entitiesoperatingunderdefinedroleswithinthe system.Inour

5. Page | 5
project,the use case diagram showsthatthere are 3 actors who are “student”,“Admin”andthe
“Assistor”.So,we can see that the “student”can registerandthenlogintothe systembutfirstthey
needtobe verified.Afterverifyingtheycanrequestservicesandthenmake paymentsforit.The
paymentcan be done inthree ways;incash, viabKash,or by credit/debitcard.The “Assistor”can
register,login,acceptrequestmade bythe “students”.The “Admin”logsinand makesthe requestvalid
and the assistorvalidforthe service tobe applied.
Activity Diagram:
ActivityDiagram: We use ActivityDiagramstoillustrate the flow of control inasystemandreferto the
stepsinvolvedin the executionof ause case.We model sequential andconcurrentactivitiesusing
activitydiagrams.So,we basicallydepictworkflowsvisuallyusinganactivitydiagram.Anactivity
diagramfocusesonconditionof flowandthe sequence inwhichithappens. We describeordepictwhat
causesa particulareventusinganactivitydiagram. Inour Project,The Activitydiagramshowsthe
activityof the student,soit startsthenthe usergivesthe informationrequiredforthe registration.After
that the useris verifiedasshowby“fork” symbol onthe diagramthat the email,passwordandphone
numberhave to be verified.Thenthe accountiseithercreatedorrejectedbasedonthe information

6. Page | 6
provided,nextthe appwill askforthe userto give permissiontolocate the areahe or she is in,thenit
will showthe availableservicesthatcanbe providedtohimor her therefore the studentorusercan
thenrequestthe service.Finally,the studentorusermakesthe paymentandisvalidforthe service.
Class Diagram:
Thisis the classdiagram of our project“HATS”. There are four(04) classeshere –User, Admin,Students,
Assistor.Afterclassname all the attributes haswritten.Allattributesare private.Thenthere are all
methodswhichisthe functionalityof classes.
User classwill inheritotherthree classes.AdminhasanassociationrelationwithStudents,Assistor
classes. He will manage AssistorandStudents.Assistorwill helpStudentsandthatisanotherassociation
relation.

7. Page | 7
Effort Estimation:
Task Duration(days) Predecessor
[-]Analysis
1. On-Site Meetings 2
2. Discussion with Stakeholders 2 1
3. Document Current Systems 6 2
4. Analysis Complete 4 3
[-]Design
5. Design Database 7 4
6. Design Software 7 4
7. Interface Design 3 6
8. Create Design Specification 2 7
9. Design Complete 2 8
[-]Development
10. Development system
Modules
4 9
11. Integrate System Modules 3 10
12. Perform Initial Testing 3 11
13. Development Complete 4 12
[-]Testing
14. Perform System Testing 2 13
15. Document Issues Found 3 14
Work Breakdown Structure (WBS)
Effort = PM = Coefficient<Effort Factor> *(SLOC/1000) ^P
= 2.4* (6000/1000) ^1.05= 15.74 =16
Development time, DM = 2.50 (PM) ^T
= 2.50 (16) ^0.38 = 7.16 = 7 weeks
Required number of people, ST = PM/DM = 16/7 = 2.28 = 2
As HATS is an organic type software, the value of Coefficient<Effort Factor> = 2.4 , P = 1.05 ,
T = 0.38

8. Page | 8
Budgeting:
Difficult (0.70) TK. 40K
HATS Build
Simple (0.30)
TK. 20K
ExpectedCost= (path probability) X (estimated path cost)
= 0.3*20 + 0.7*40 = TK.34k
Budgetingisveryimportantpartfor developingoursoftware projectHATS.If we don’tcalculate our
expectedcosttheninfuture itwill create problem.Forexamplewe don’tknow how muchmoneyis
neededtodevelopourHATSprojectbut we start to developoursystem.Afterworkingone monthon
thisprojectwe findthatwe don’thave enoughmoneytofinishthe project.Thenitwill be veryharmful
for our developerteam.Andwe won’tbe able tocontinue the project.Forthisreasonwe have
calculatedourexpectedcosttocomplete the project.
As we are buildingourprojectandthisis a freshnew project,fromsome surveywe findbuildinganew
systemcan be cost 40K taka fordifficultpartand20K taka forsimple part.We considerthat ourdifficult
part of the systemis70% and simple partis30%. Soour calculatedexpectedcostformakingHATS is34K
taka.
Scheduling:
All Task Name Week1 Week2 Week3 Week4 Week5 Week6 Week7
1 [-] Analysis
2 On-Site Meetings
3 DiscussionwithStakeholders
4 Document Current Systems
5 AnalysisComplete
6 [-] Design
7 Design Database
8 Design Software
9 Interface Design
10 Create Design Specification
11 Design Complete
12 [-] Development
13 Development systemModules
14 Integrate System Modules
15 Perform Initial Testing
16 Development Complete
17 [-] Testing
18 Perform System Testing
19 Document Issues Found
20 Correct IssuesFound

9. Page | 9
We have dividedourHATSprojecttaskinfour parts.These are Analysis,Design,Development,and
Testing.InAnalysispartwe will analyze projectrequirements.We will attendmeetingwithour
developerteam.We will make documents.We willidentifystakeholdersandwill be completedintwo
weeks.InDesignpartwe will designourdatabase forHATS.Andthenwe will startdesigningthe system.
We will create designspecification.Anditwill be completedintwoweeks.InDevelopmentpartwe will
developoursystemmodules.We willintegrate systemmodules.Andthe lasttaskisperforminginitial
testing.Andthispartwill alsobe completedintwoweeks.The lastpartis testing.Inthispartwe
performouractual systemtesting.Andthiswillbe completed inone week.
Task: Person Week1 Week2 Week3 Week4 Week5 Week6 Week7
1-5: Rokon
1-5: Shakib
6-11: Fariha
6-11: Rokon
12-16: Udoy
12-16: Shakib
17-20: Udoy
ActivityKey:1-5:Analysis
6-11: Overall Design
12-16: Developing System
17-20: System Testing
We are four membersinourteamto developthe HATS.We have dividedourtaskinfourparts. Rokon
and Shakibwill complete the Analysis part,FarihaandRokonwill complete the designpart,Udoyand
Shakibwill complete the developingpart.AndUdoywill complete the testingpart.
Risk Analysis
As Projectplansare basedonassumptions.The riskof the assumptionbeingwrongisalwayspresent.
Whenthe risk happens,itbecomesaproblemora potential issue.Risksare potential problemsthat
mightaffectthe successful completionof asoftware project.Inthe HATS project,we are followingthe
reactive riskmanagement.So,we willfix aproblemwhenwe face itandplanforresourcestonarrow
downthe damages.One of the main risksof thisprojectishow to come up withmoneywhenitexceeds
the expectedcostwe predicted.There are several more riskandaswe analyzedthem, here are the
probabilityof themhappening: -

10. Page | 10
Risk Category Probability Impact
Staff Shortage ST 80% 3
Lack of experience instaffs ST 60% 3
Lack of properequipment DE 60% 2
Users largerthanexpected PS 40% 2
Notbeingable toshow “newness”tocustomers TE 20% 1
Bad analysisof time andcost estimation CU 80% 1
How far can the product give servicestocustomers PR 70% 3
By, analyzingthe risksassociatedwiththe project,we cansaylack of experiencedstaff are 60% as a
resultoutlosswouldbe about15000tk, so if we try to bringinmore staff the costingwouldbe about
5000tk andthiscuts downthe riskby30%
So,if we use the equationRRL,
=> ((0.60x15000) - (0.30x15000))/5000
=> 7500/5000
=> 1.5
As RRL>1, so we shouldgo forthissolutionif Iteverraises.
“EveryRiskis worthtakingif as longas it’sfor a good cause and contributestoa goodlife”
-RichardBranson