software engineering jargons
understanding basics
comptency framework
cultural entity
cultural event
cultural managment
cultural roles
engineering roles
leadership
organisational culture
people needs
professional development
project culture
project needs
stake holders
team cohesion
time log
implement process
extreme programming
KISS -
process assessment
product concurrency
requirements volatility
risk assessment
tailoring
thrashing
tools
normailise
training method
controld measurements
indicators
predictive measurements
process measurements
product measurent
project measurement
Vision
benefits
features/resources/time triangle
needs
risks
software project outline
tradeoffs
oragnise your resources
deployment
hardware resources
rebuild
software upgrades
support
schedule
cost drivers
immovable milestone
integratable
meetingless projects
write your plan
CMM
feature creep
quality assurance
Software development plan
target environment
roles
commitments
dependencies
lead role
supporting role
overlapping roles
schedule
core functionality
just in time approach
rework
tiger team
up front tasks
work break down structure
support
acquisition schedule
purchase order
resources
cultural status
drop dead date
engineering status
micromanaging
process reduction
proces visibility
refocus
task status
work-around
action plan
blame game
group think
manager's checklist
project view
archive
best case
champion
likely case
worst case
acceptance testing
ad hoc testing
code review
cohesion
core functionality
coupling
critical path
design consistency
extendability
implementation plan
information hiding
insulation
maintainability
modularity
portability
software engineering practices
completion criteria
dry run
iceberg effect
software environment
data poor
project history
0 Comments:
Post a Comment
<< Home