PDF Archive

Easily share your PDF documents with your contacts, on the Web and Social Networks.

Share a file Manage my documents Convert Recover PDF Search Help Contact



SEUnit4 .pdf



Original filename: SEUnit4.pdf
Author: ILOVEPDF.COM

This PDF 1.5 document has been generated by ILOVEPDF.COM, and has been sent on pdf-archive.com on 23/08/2015 at 15:31, from IP address 103.5.x.x. The current document download page has been viewed 313 times.
File size: 192 KB (6 pages).
Privacy: public file




Download original PDF file









Document preview


Software Engineering

10IS51

UNIT 4
SYSTEM MODELS, PROJECT MANAGEMENT

System models
System modeling : System modeling helps the analyst to understand the functionality
of the system and models are used to communicate with customers
Different models present the system from different perspectives
• External perspective showing the system’s context or environment
• Behavioral perspective showing the behavior of the system
• Structural perspective showing the system or data architecture
Structured methods
• Structured methods incorporate system modeling as an inherent part of the method
• Methods define a set of models, a process for deriving these models and rules and
guidelines that should apply to the models
• CASE tools support system modeling as part of a structured method
Context models
• Context models are used to illustrate the boundaries of a system
• Social and organizational concerns may affect the decision on where to position
system boundaries
• Architectural models show the a system and its relationship with other systems
Process models
• Process models show the overall process and the processes that are supported by
the system
• Data flow models may be used to show the processes and the flow of information
from one process to another
Behavioural models
• Behavioural models are used to describe the overall behaviour of a system
• Two types of behavioural model are shown here
• Data processing models that show how data is processed as it moves through the
system
• State machine models that show the systems response to events
• Both of these models are required for a description of the system’s behaviour
Data-processing models
• Data flow diagrams are used to model the system’s data processing
• These show the processing steps as data flows through a system
• Intrinsic part of many analysis methods
• Simple and intuitive notation that customers can understand
• Show end-to-end processing of data
Object models
• Object models describe the system in terms of object classes

Page 22

Software Engineering

10IS51



An object class is an abstraction over a set of objects with common attributes and
the services (operations) provided by each object
• Various object models may be produced
• Inheritance models
• Aggregation models
• Interaction models
Object models
• Natural ways of reflecting the real-world entities manipulated by the system
• More abstract entities are more difficult to model using this approach
• Object class identification is recognised as a difficult process requiring a deep
understanding of the application domain
• Object classes reflecting domain entities are reusable across systems
The Unified Modeling Language
• Devised by the developers of widely used objectoriented analysis and design
methods
• Has become an effective standard for objectoriented modelling
• Notation
• Object classes are rectangles with the name at the top, attributes In he middle
section
and operations in the bottom section
• Relationships between object classes (known as associations) are shown as lines
linking objects
• Inheritance is referred to as generalisation and is shown‘upwards’ rather than
‘downwards’ in a hierarchy

Project Management
It is concerned with activities involved in ensuring that software is delivered on time
and on schedule and in accordance with the requirements of the organisations
developing
and procuring the software
Project management is needed because software development is always subject to
budget and schedule constraints that are set by the organisation developing the
software
Software management distinctions
• The product is intangible
• The product is uniquely flexible
• Software engineering is not recognized as an engineering discipline with the same
status as mechanical, electrical engineering, etc.
• The software development process is not standardised
• Many software projects are 'one-off' projects
Management activities
• Proposal writing includes Feasibility, Project costing, Overall requirements
(Internal and External), terms and conditions
• Resource requirements also include Personnel selection
Page 23

Software Engineering




10IS51

Project planning and scheduling
Project monitoring and reviews also including Personnel and Process evaluation
Report writing and presentations

Project staffing involves the following
• May not be possible to appoint the ideal people to work on a project
• Project budget may not allow for the use of highlypaid staff
• Staff with the appropriate experience may not be available
• An organization may wish to develop employee skills on a software project
Managers have to work within these constraints especially when (as is currently the
case) there is an international shortage of skilled IT staff
Project planning




Probably the most time-consuming project management activity
Continuous activity from initial concept through to system delivery. Plans must be
regularly revised as new information becomes available
Various different types of plan may be developed to support the main software
project plan that is concerned with schedule and budget

Types of project plan

Project plan structure – It should include the following:
• Introduction
• Project organization
• Risk analysis
• Hardware and software resource requirements
• Work breakdown
• Project schedule
• Monitoring and reporting mechanisms
Activity organization
• Activities in a project should be organized to produce tangible outputs for
management to judge progress
Page 24

Software Engineering




10IS51

Milestones are the end-point of a process activity
Deliverables are project results delivered to customers at the end of some major
project phase such as specification or design
The waterfall process allows for the straightforward definition of progress
milestones

Project scheduling
• Split project into tasks and estimate time and resources required to complete each
task
• Organize tasks concurrently to make optimal use of workforce
• Minimize task dependencies to avoid delays caused by one task waiting for
another to
complete
• Dependent on project managers intuition and Experience

The project scheduling process

Scheduling problems





Estimating the difficulty of problems and hence the cost of developing a solution
is hard
Productivity is not proportional to the number of people working on a task
Adding people to a late project makes it later because of communication
overheads
The unexpected always happens. Always allow contingency in planning

Page 25

Software Engineering

10IS51

Activity network

Risk management
• Risk management is concerned with identifying risks and drawing up plans to
minimize their effect on a project.
• A risk is a probability that some adverse circumstance will occur.
• Project risks affect schedule or resources
• Product risks affect the quality or performance of the software being developed
• Business risks affect the organization developing or procuring the software
The risk management process
• Risk identification
• Identify project, product and business risks
• Risk analysis
• Assess the likelihood and consequences of these risks
• Risk planning
• Draw up plans to avoid or minimise the effects of the risk
• Risk monitoring
• Monitor the risks throughout the project
Risk identification
• Technology risks
• People risks
• Organizational risks
• Requirements risks
• Estimation risks
Risk analysis
• Assess probability and seriousness of each risk
• Probability may be very low, low, moderate, high or very high
Page 26

Software Engineering


10IS51

Risk effects might be catastrophic, serious, tolerable or insignificant

Risk planning
• Consider each risk and develop a strategy to manage that risk
• Avoidance strategies
• The probability that the risk will arise is reduced
• Minimization strategies
• The impact of the risk on the project or product will be reduced
• Contingency plans
• If the risk arises, contingency plans are plans to deal with that risk

Page 27


Related documents


sesyllabus
it sem6 se assignments
seunit2
seunit5
seunit4
05773106


Related keywords