Software Engineering 1 Week 9

1
Software Engineering 1 Week 9

• By Brent Acworth

2
Agenda

• Introduction
• Software Engineering 1
• Software Engineering Stream
• 3rd Year Project (General Course Overview)
• Standards
• Roles in projects
• Panel Discussion (Genetic Software Engineering vs
  Other Design Methods)

3
Introduction

• I work for the SQI
• Honours year in B. Software Engineering
• Tutor SE2, P1, Project Management ect
• My interests in computing lie in software process
  improvement

4
Software Engineering 1

• Ability to play the game
• Subject content and applicability
• Assignments
• Exam

5
Software Engineering Stream

• Software Engineering 1
• Software Quality Principles (Software Quality
  Characteristics, Quality Model Construction)
• Software Engineering 2 (Formal Methods, XML, PHP,
  OO Concepts)
• Software Architecture (High Level Architecture
  including horizontal and vertical Architecture,
  Interfaces)

6
3rd Year Project

• A project can cause problems amongst friends and
  cause enemies.
• The project was very difficult and time consuming
  for only having four team members, we recommend
  that a minimum of five team members for each team
  next year. We do agree that all the work
  performed was required, though it increased
  workloads dramatically.

7
3rd Year Project

• Needed more contact with the CMM and the defined
  processes and how effective the processes were.
• Design process was very appropriate for
  reengineering of software.
• It is necessary to have a clear distinction
  between roles to prevent peoples excessive and
  lack of work by individual members.
• Excessive documentation to meet the Universities
  curriculum not the Clients needs and wants.

8
3rd Year Project (Design 3)
9
3rd Year Project (Program Pics)
10
3rd Year Project (Program Pics)
11
3rd Year Project (Program Pics)
12
Standards

• ISO/IEC 9126 Software engineering Software
  quality
• ISO/IEC 122071995 (ISO/IEC 12207) Standard for
  Information Technology Software life cycle
  processes
• ISO/IEC 15504 TR Information Technology Process
  Assessment
• Also many other applicable standards (SRS, PDP
  ect.)

13
Roles In Projects (Project Management)

• The purpose of the Project management process is
  to identify, establish, coordinate and monitor
  activities, tasks and resources necessary for a
  project to produce a product and/or service
  meeting the requirements. As a result of
  successful implementation of the process
• the scope of the work for the project will be
  defined
• the feasibility of achieving the goals of the
  project with available resources and constraints
  will be evaluated
• the tasks and resources necessary to complete the
  work will be sized and estimated
• interfaces between elements in the project, and
  with other projects and organizational units,
  will be identified
• and monitored
• plans for execution of the project will be
  developed and implemented
• progress of the project will be monitored and
  reported
• actions to correct deviations from the plan and
  to prevent recurrence of problems identified in
  the project will
• be taken when project targets are not achieved.

14
Roles In Projects (Configuration Management)

• The purpose of the Configuration management
  process is to establish and maintain the
  integrity of all the work products of a process
  or project. As a result of successful
  implementation of the process
• a configuration management strategy will be
  developed
• all items generated by the process or project
  will be identified, defined and baselined
• modifications and releases of the items will be
  controlled
• the status of the items and modification requests
  will be recorded and reported
• the completeness and consistency of the items
  will be ensured
• storage, handling and delivery of the items will
  be controlled.

15
Roles In Projects (Risk Management)

• The purpose of the Risk management process is to
  identify and mitigate the project risks
  continuously throughout the life-cycle of a
  project. The process involves establishing a
  focus on monitoring of risks at both the project
  and organizational levels. As a result of
  successful implementation of the process
• the scope of the risk management to be performed
  for the project will be determined
• appropriate risk management strategies will be
  defined and implemented
• risks to the project will be identified in the
  project strategy, and as they develop during the
  conduct of the project
• the risks will be analyzed and the priority in
  which to apply resources to monitor these risks
  will be determined
• risk metrics will be defined, applied, and
  assessed to determine the change in the risk
  state and the progress
• of the monitoring activities
• appropriate action will be taken to correct or
  avoid the impact of risk.

16
Roles In Projects (Quality Assurance)

• The purpose of the Quality assurance process is
  to provide assurance that work products and
  processes of a process or project comply with
  their specified requirements and adhere to their
  established plans. As a result of successful
  implementation of the process
• a strategy for conducting the quality assurance
  process activities and tasks will be developed,
  implemented and maintained
• evidence of quality assurance activities and
  tasks will be produced and maintained
• problems or non-conformances with contract
  requirements will be identified
• adherence of software products, processes and
  activities to the applicable standards,
  procedures and
• requirements will be verified objectively.

17
Roles In projects (Other)

• Client Liaison
• Verification Manager
• Validation Manager
• Communication Manager
• Technical Manager
• Metrics Manager (My Area of Research)

18
Panel Discussion

• Genetic Software Engineering vs Other Design
  Methods
• 4 participants (outspoken, 2 that like Genetic
  Software Engineering and 2 that dont)
• Fire panel with questions