This note collect all terms occur in SEPP Lecture 1/2/4/5. It would be helpful to recap what has learnt and what has already been abstracted away.
small system, budget, reliability, complex interface, software development, requirement capture, design, construction, implementation, testing, debugging, maintenance, evolution, management, software engineering activity
needs, issues, stakeholder, prioritization, maintenance, evolving requirement, modelling language, UML, multiple level, architectural design, high-level design, detailed design, coding, unit test, code evolution, documentation, customer acceptance testing, cost, post release change, enhancing, coping with changing world, maintainability
ordering activities, outcomes of activities, arrangement of people & resources, planning in advance of execution, predicting cost/time/resources, risk reduction, monitoring, enabling their own adaptation
automating, business process, project based engineering, product based engineering, execution model, software product, stand-alone model, hybrid execution model, software as a service model, reusable software
waterfall process, linear sequential life cycle model, plan-driven process, plan, change, unchangeable world, stage, safety system, embedded system, long lifetime system
agile process, iteration of development, testing the software development process, communication, customer, developer, manager, tester, motivated individual, customer collaboration, unfinished features, most important features, iterative planning, honest plan, daily communication, working software
customer satisfaction, rapid delivery, principal measure of progress, daily co-operation, face-to-face conversation, continuous attention, technical excellence, good design, simplicity, self-organizing team, regular reflection on process, regular reflection on tuning of behaviour
high/low criticality, senior/junior developer, culture, order, culture that responds to change, culture that demands order
software requirement, organisation, requirements engineering, systematic handing of requirement
functional requirements, non-functional requirements, ‘ilities’, efficiency, security, portability, usability, user experience, distinction
person, group, end user, customer paying for software, government regulator, system architect, software developer, software tester
elicitation, analysis, specification, validation, strict sequence, project failure
elicitation source, goal, domain knowledge, business rule, operational environment, organizational environments, interview, scenario, prototype, facilitated meeting, observation, conflict, single consistent set of requirement, careful structured English, use case model, supporting text, formal specification, mathematically-based language, release, consistency check, completeness check, realism check, verifiability, measurable non-functional requirement
use case, system’s behaviour, user, viewpoint of user, unit, coherent unit of functionality, actor, human user, external system, external device, further information, primary actor, messages, supporting actor, use case scenario, instance, guarantee, main success scenario, alternate success scenario, failure scenario, common user goal, trigger, pre-condition, assumption, stick figure, named oval, interaction, requirement specification, iterated requirement elicitation
graphical language, UML model, model-driven development, granularity, abstraction
enabling their own adaptation, regular reflection, tuning of behaviour