A level key:
Team structure:
Chief programmer team
A person designated skilful
master programmer
, lead the team. The advantages and disadvantages of this model are reflected in the
exchange path
on.
If the
project size small
or lead programmer
of ability
, you get
a very high work efficiency
Complex project
or master programmer
lack of capacity
, then there will be
a bottleneck
Democratic team
There is no centralized bottleneck, each member can play a
dynamic role
,
improve morale and a sense of accomplishment
Work as efficient as chief programmer team,
unify their thinking
and
resolving conflicts
cost quite a lot
Agile processes on the use of this form
Open Team
Black-box management
mode. Focus on
self-management
, motivation member of the
initiative
, play members of the
innovation
ability. The disadvantage is that no
visibility
Team Building (P53)
The establishment of charter
:
goals
, common pursuit, structure and division of labor, activity and task performance,
rules
and constraints
Continued success
: improve morale, trust, confidence. Method:
recreational activities
, milestones
Harmonious communication
: the establishment of the system and
open environment
.
The meeting
is an effective means
Avoid Team Killer
: Avoid prevention management, bureaucracy, geographically dispersed, dispersion time, reduce product quality, false deadline, a small circle
Software Quality Models:
Feature
Completeness
: a software
necessary
and
sufficient
degree of functionality, these features to meet user needs
Correctness
: software features that can be
accurately
determined the extent of
Security
: Detect and
prevent
information
leakage
, information
loss
,
illegal
use of system resources,
destruction
of degree
Compatibility: without needing a change in environment and conditions, the extent of the new software can be installed
Interoperability: connected to the operation of the other systems with ease
reliability
Freedom from defects: not contain undetected errors
Fault Tolerance
: software
continue to work
, the extent detrimental to the user's system failure does not occur. Including software contain downgrade and
restore
the degree of functional
Availability
: after a system failure
to maintain operational
capability
Ease of use
Comprehensibility: Understanding the software effort it takes
Easy to learn: the understanding of the software with minimal effort it takes
Operability: operation environment, the degree of matching the user's physiological characteristics
Communications: the degree of design and physical characteristics consistent
effectiveness
Ability within the appropriate time limits, performing a specified function: Time Economy
The ability to use the appropriate amount of resources to perform the specified functions: economic resources
Maintainability
(software maintenance: can be changed scalable test)
Energy correction and error handling software takes the user comments: revisability
Scalability: to improve or modify the software takes energy efficiency
Software testing effort it takes: testability
portability
Hardware independence: the degree of independence of a particular hardware environment
Software Independence: independent of the degree of specific software environment
Can be installed: the new environment suitable for energy it takes
Reusability: application level than the original application multiplexed
ISO Quality Model:
The exact extent of the software in accordance with the terms of: accuracy
Compliance: software complies with the statutory standards, the degree of agreement, rules or other similar provisions
Suitability: function specified task exists and functions of appropriateness
Maturity: the degree of failure frequency due to software defects resulting from
Recoverability: Software rebuilding its performance level after the failure, which affected the ability to recover data
Attractiveness: the ability to attract users
Energy diagnostic software defects, analyze the cause it takes: analyzability
Changeability: functional modification takes effort
Stability: Because modifications lead to unexpected results of the level of risk
The ability to not need to take additional activities or means will be able to adapt to different environments: Adaptability
Coexistence: a public environment with other independent software ability to share common resources coexist
Interchangeability: In another environment, the software needs to replace the energy it takes
Quality verification
methods :( racking our brains, laboratory, scientific)
review, testing and quality metrics
(22332)
Configuration management activities
:
Identifies the configuration items
Version Management
Change Control
Configuration Audit
status report
Software Release Management
Review stage
Planning stages
The overall deployment phase
Preparation Phase
Stage Review Conference
Rework stage
Tracking stage
Baseline: has been
through a formal review
of
specifications
or
products
, it can be
used as a basis for further development
, and can only be changed through a formal change control process
Class B:
Configuration Management
: The
technical and management
guidance and supervision of
methods
,
identify
configuration items
functional and physical characteristics, and
control
of these features
change
,
record
and report
change processing
and
state
,
validation and consistency requirements specification
Starter Edition: a
technical
approach,
identify
configuration item,
control changes
,
record the change
,
verify
the requirements specification of
consistency
The importance of software development
products and change
into management and
monitoring
, without affecting the development of collaborative activities effectively
deal with change
Configuration items: the need for configuration management of
software development products
(documentation, source code, data)
Management
Documentation
Review
documents
Software
Documentation
Source
Environment: For data files
C:
Project features:
Clear
objectives
(Why)
Duration
(time)
Cost
and resources (how about - the cost)
Types of work
(who)
Team feature
Common
goal
Shared
responsibility
Skills
complementary
Small
groups
Clear
structure
Process: Demand - Architecture - detailed design - construction - Tests (demand - low high school three code - test)
Goal of project management:
goals
,
time
,
cost
,
resources
, customer
acceptance
Project management process groups: the project
started
, project
planning
, project
execution
, project
tracking and control
, project
closeout
