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
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

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

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Requirement - software requirment, Assignments of Introduction to Software Engineering

Addis Ababa UniversityIntroduction to Software Engineering
Prof. Adrew Abyenhr

Software engineering is an engineering discipline

Typology: Assignments

2020/2021

Uploaded on 03/29/2021

bethel-yohannes
bethel-yohannes 🇪🇹

2 documents

1 / 8

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1 Introduction
1.1 Objectives -------------------------------------------1
1.2 Constraints-------------------------------------------1
2 Project Scope -------------------------------------------2
2.1 Functions ----------------------------------------------2
2.2 Features --------------------------------------------------2
2.3 Constraints ------------------------------------------------2
2.4 Interface -----------------------------------------------------2
3 Project organization -----------------------------------------3
3.1 Project Team ------------------------------------------------3
3..2 Roles and Responsibilities --------------------------------3
4 Risk analysis-----------------------------------------------------4
4.1 Risks-------------------------------------------------------------4
4.1 Assess and Reduce----------------------------------------------4
5 Resource requirements -------------------------------------------5
5.1 Software Requirement -----------------------------------------5
5.1 Hardware Requirement -----------------------------------------
6 Work Breakdown Structure (WBS), Estimation and Scheduling ----------6
6.1 Milestone----------------------------------------------------------------------
6.2 Deliverable ---------------------------------------------------------------
7 Project schedule ------------------------------------------------------
7.1 Size Estimation and Effort Estimation ----------------------------------
7.2 Schedule ----------------------------------------------------------------
7.3 Gantt Chart ----------------------------------------------------------------
8 References ---------------------------------------------------------------- 8
pf3
pf4
pf5
pf8

Partial preview of the text

Download Requirement - software requirment and more Assignments Introduction to Software Engineering in PDF only on Docsity!

1 Introduction

1.1 Objectives ------------------------------------------- 1.2 Constraints-------------------------------------------

2 Project Scope -------------------------------------------

2.1 Functions ---------------------------------------------- 2.2 Features -------------------------------------------------- 2.3 Constraints ------------------------------------------------ 2.4 Interface -----------------------------------------------------

3 Project organization -----------------------------------------

3.1 Project Team ------------------------------------------------ 3..2 Roles and Responsibilities --------------------------------

4 Risk analysis -----------------------------------------------------

4.1 Risks------------------------------------------------------------- 4.1 Assess and Reduce----------------------------------------------

5 Resource requirements -------------------------------------------

5.1 Software Requirement ----------------------------------------- 5.1 Hardware Requirement -----------------------------------------

6 Work Breakdown Structure (WBS), Estimation and Scheduling ----------

6.1 Milestone---------------------------------------------------------------------- 6.2 Deliverable ---------------------------------------------------------------

7 Project schedule - -----------------------------------------------------

7.1 Size Estimation and Effort Estimation ---------------------------------- 7.2 Schedule ---------------------------------------------------------------- 7.3 Gantt Chart ----------------------------------------------------------------

8 References ---------------------------------------------------------------- 8

1 Introduction

1.1 Objectives Human Resources planning is a process by which management determine how the organization should move from its current manpower position to its desired manpower position. Through planning, management strives to have the right number and the right kinds of people, at the right place, at the right time, doing things, which result in both organization and the individual receiving maximum long-run benefits. Human resource planning involves getting the right number of qualified people into the right jobs at the right time .It involves Identifying and acquiring the right number of people with the proper skills ,motivating them to achieve high performance, creating interactive links between business objectives and resource planning activities. The objective of HRMS can be define as managing employees's data in different role types and store information efficiently. our system is expected to solve a problems such as data loss, Schedule ,corruption and efficiency problem.

1.2 Constraints

. There are many uncertainties’ about the future: - Due to everyday

uncertainties'’, human resource planning can only be a guiding factor.

. Top management resistant to change/lack of support: - Can be very difficult to

implement the changes in the organisation if management does not support the

decisions made by the human resource department.

. Inadequate development programmes: - Need implementation of programmes

that a learning atmo create sphere for employees in the organisation; like career

planning, job training, development programmes. Often programmes are

limited to lectures and expected results not met.

. Accuracy

2 Project Scope

2.1 Function

Functions are the task our system expected to do and these are

  • Job design and job analysis

Job design involves the process of describing duties, responsibilities and

operations of the job. To hire the right employees based on rationality and

research, it is imperative to identify the traits of an ideal candidate who would

be suitable for the job. This can be accomplished by describing the skills and

character traits of your top-performing employee

3 Project organization

3.1 Project Team Name (^) Roles Emails Bits Collage Client Bethelhem Demisa Project manager, Designer team,quality team and promoter team Coordinates and guides the team leaders.

  • Forming team and assigning tasks
  • Managing the time budget;
  • Do project planning, estimation and project schedule
  • Control and manage the project by coordinating activities
  • Keeps track of internal progress and exchange relevant
  • information by means of team leader meetings (Monitoring and organizing these meetings).
  • Resolve the issues on the project Closing the project Bethelhem Murad Designer team, Designer team, System model manger
  • Design the system with team
  • Controlling the team of designers
  • Make a report every week on the design Adenawit Mulken Programing team ,Requirement analysis leader, System model manger, Quality t.
  • Control the programming team
  • Generate report on the progress of the system
  • Approved the code which is submitted by teams
  • Develops and maintains the implementation standards
  • Reviews designs for completeness prior to implementation
  • Establishes and maintains control over the implemented product
  • Submit report to project manager Bethel Yohannes Configuration team leader, Configuration team
  • Control the programming team
  • Generate report on the progress of the system
  • Approved the code which is submitted by teams
  • Develops and maintains the implementation standards
  • Reviews designs for completeness prior to implementation
  • Establishes and maintains control over the implemented product
  • Submit report to project manager Kaleab Alemu Promoter leader Promoter team
  • Collect requirement for analysis.
  • Make monthly report.
  • Analyze and defines system and/or project specific requirements
  • Maintains requirements control
  • Analyses Gathered information

4 Risk analysis

Risk impact on schedule/cost Methods to overcome it

privacy and security giving higher priority for

secured system and make

sure all privacy terms are

conserved

Data vulnerability it might lead customers to

lose their believe in

predicts the effort needed to build it. The relationship between he size of

software and the effort required to produce it is productivity. Our system human

resource system so we need 30KLOC by estimating and once we know the size

we can estimate the effort and the time by cocomo model

since our project organic project we find the effort

Ei = a1(KLOC)

a PM where a1 and a2 are constant factors historical data for simple projects, they are constant factors that vary for different types of projects like: intermediate, large projects Ei = 2.4*(30)

PM Ei = 85.34 PM M can be used to adjust the basic estimate by including expert knowledge of the specific attributes of this project. Potential attributes/constraints to consider include:

  • Product attributes (e.g. reliability)
  • Computer attributes (e.g. memory constraints)
  • Personnel attributes (e.g. programming language experience)
  • Project attributes (e.g. project development schedule) Initial estimate is 85.34 person-months, Estimates of the effect of various constraints or attributes: Attribute Magnitude Multiplier(M) Reliability V High 1. Memory constraint High 1. Tool use Low 1. Schedule Accelerated 1.

(EAF) becomes: 1.01* 1.4 * 1.1* 1.23 = 1.

E = Initial estimation (E i ) * EAF

E = 1.91*85.34 = 163.26 man month

Now we have effort adjustment factor and initial estimation of our project, so

now we can

define the duration (D) it takes to complete the total project.

Using COCOMO model:

D = C * E

d

Where C and D are constant factors; They have the value of 2.5 and 0.

respectively for simple

projects.

D = 2.5*(163.26 )

D = 17.33 month

No of peoples required can be determined by using the formula:

N= E/D

N = 163.26/17.

N = 9.42 people

Though the project to be developed consumes a time duration of above

seventeen months for a single person depending on the above calculation. Our

team has 7 members so we can have finalized with 2 months.