Software Engineering: to guide software development and maintenance of an engineering discipline the three elements of methods / tools / development process value : promote project success
Modern product development three principles : utility, feasibility, desirability software process is a core component of software engineering.
Iteration: Repeated incremental refinement: block by block construction needs survey methods: research documents, interviews, field observations, questionnaires, prototyping
Classic Software Process: Waterfall, RUP Rational Unified Process, Scrum agile process, the expansion process ICONIX
Waterfall model : requirements analysis, requirements definition, preliminary design, detailed design, implementation, system testing, acceptance testing, maintenance
UML bearing surfaces subject thought. FIG Static : FIG Object / FIG class / component diagram / deployment FIG; Dynamic FIG : use case diagram / sequence diagram / activity diagram / state of FIG / collaboration FIG.
Demand is the basis for successful software, requirements engineering is a means to address the needs of a nightmare: the needs of the development / investigation / analysis / definitions / Management / Confirmation / Tracking / Change Control
Requirements Development (capturing user needs / defining product requirements, find the pain points suggest ways) needs survey needs analysis (defined vision, business modeling, use case analysis) requirements definition: specification ((non) functional requirements) demand management (customer and developer common understanding of the needs, maintaining consistency with other results, control change)
Three types of people demand : the boss strategy / cut costs / fixed vision; Manager: simplify management processes to optimize business modeling; business modeling; employees: Working with a simple analysis of cases
ICONIX process :( cut costs drive cases) vision, business modeling (use case / status FIG sequence / improvement) needs analysis (System / domain) robustness analysis (FIG robustness updated domain model) key design final design (design details) implementation ( domain model -> update -> static FIG class)
Features: Early coding and shorter design cycles. Simplify RUP process. Agile thinking.
RUP is a lightweight compared with the process. And agile than the provision of adequate demand for design documents, but not overly analysis and design.
Gets vision : to find a project leader (the most powerful stakeholders) to obtain the desired (pay purposes) describe metrics
Business Modeling step clear for whom services (improvement of the organization) from the outside to see what the status quo: the organization is a collection of value; from the inside is a collection of system. Improve
Business Modeling sense to shift the perspective of the customer, clear and accurate diagnosis. Clear for whom the service, do not do for themselves; the status quo organization / inadequate pain; how to improve / resolve.
Business use case diagram : Help from a high-level understanding of the organization's business composition. Business executives: Enjoy value; business organizations: the value provided.
FIG service sequence (to help understand the business processes from the details of the organization) with a period corresponding to the process in Example advantage: the idea of object-oriented view of business processes
Role: identifying the business object: to determine responsibilities between business objects, collaboration and interaction sequence; understand the status of business by sequence diagrams, provide the basis for optimized business
Composition: business executives; service workers; business entities; call messages; return message commonly branches: circulation loop, branch alt, an optional opt
Improvement anew system is introduced as an entity existing processes, the process may be improved view, the evaluation results of improvement
2 understand the purpose, improvements found point: automatic transfer information, complex logic package, the transfer of responsibility, the operation business objects (Management System)
The results of the review (of all participants to reach a consensus needs to sign it or rework) Objective: To improve the modeling results, look for missing the wrong place, correction, you can go back and continue to do business modeling iteration. The key stakeholders in the information and reach consensus, signature confirmation, the next phase of the startup flag.
Domain modeling step of extracting noun phrases, repeats the similar negative, and the negative range of the system itself, the first edition, first edition finishing domain model
Meaning the glossary terms to ensure clear and consistent communication. The term & than ordinary: illustration of the embodiment, the term clearly show the relationship between the evolution of the third correction perfect final static class diagram
Domain Model Data Model
Domain Model: Model analysis tool understanding of relationships between entities; Data Model: System Design part, describe the implementation of the data structure of user needs
System Composition: Main Actors: initiator, to realize its secondary Actors: PRO; Support (background) 3 system boundary, system use case, the relationship between the use cases
Case modeling systems meaning the perspective of the new steering system, standing on the end-user point of view the problem is the modeling of the value of the new system for the implementation of the system provided by
Step Example rendering systems : a system boundary is determined by the second identification system to perform recognition system with Example 3, perform an action, are performed to generate the results observed value
Example Relationship use comprising: a package similar to a set of actions to be reused. Generalization: inheritance. Extended: a relatively independent and optional action
A large number of use case ≠ functions / steps (use case is the executor desire, a lot of steps) Subcontracting : by performer, by subject, by the development team, according to published case
System use case describes stakeholder interests (client: Simple bank: safety laws: to protect) the basic path (customers most want to see "were moving the name" subject is the executor or system) expansion path (accident branch) business rules (limits) non-functional requirements: to achieve the degree of functional requirements: what to do
Software Requirements Specification: accuracy, necessity, priority, clarity, testability, integrity, consistency, modifiability
Needs assessment:
1 interim review (Review and the user's daily communication) 2 check (cross product comments to each other) 3 pair programming / walkthrough / review / review 4 Planning: Who participated in / what 5 general meeting reviewed 6 up 7 Review Conference: Exposure to discuss issues 8 rework: anti-formalism 9 track: problem solving avoid recurrence
Robustness analysis of three elements: border controller class class class entity
Rule 1 performs only those boundary and the second boundary call controller and the controller 3, and a controller 4 and a controller entity
Robustness steps : Create View embodiment the connection between the text, the basic path, performer, boundary objects and entity objects, the controller, with the element, propagation path.
Robustness advantages : 1 object-oriented illustrated example, use cases and object linking up 2 points out how objects interact with each other 3. Ensure that the use case text correctly, provide a health check 4. Consider the use cases to help ensure all the necessary expansion path, provided 5. full properly check the object can be found in analysis and design 6. narrow gap
Value: Help improve results use cases. Perfect domain model, as excessive technical requirements analysis to system design
The key design sense : look for interactions between objects, distributed method. FIG embodiment comprises use described, robustness analysis FIG.
Non-functional requirements: reliability, availability, performance, supportability
High cohesion: a software module consists of a strong correlation between the composition of the code, it is only responsible for a task, a good cohesive module just do one thing, a single responsibility principle
Low coupling : direct dependency between metrics module, the interface between the modules and the module should be small and simple, such as a more complex relationship, dividing the module, in combination with beneficial modifications
Detailed design (coding test deployment maintenance upgrades) technology architecture: language development, network topology security, architecture, hardware environment, software environment
Agile Manifesto Agile philosophy + = + good practice specific application (the basis for agile origin, reveals the development of better ways to rethink the development of value and how to better work, is people-centered / iterative / incremental development methodology)
1) Individual and interactive> processes and tools 2) working software> comprehensive documentation 3) Customer Collaboration> contract negotiations 4) in response to changes> following a plan
(Software: complexity / consistency / variability / invisibility) there is a change Agility: change change managers \ team members
There are good features list DEEP features : appropriate levels of detail, emerging, did estimates, prioritize.
Scrum Product Owner, scrum coach, team
1) product managers and development of consensus-building products business goals 2) Product Owner establish the maintenance requirements list (constantly changing new), priority ranking 3) Product Owner before each iteration, screening selected high-priority needs round development 4) development team refine the iterative requirements , in accordance with the priority order iteration is complete 5) development team daily legislature / feature development / continuous integration , the progress of the development truly transparent (daily Legislative Council) 6) product Owner for each iteration delivery the software can work on-site inspection feedback (iterative review meeting) 7) within the team conducted the current round of review, improvements can be found under the guidance of an iteration (iteration retrospectives)
Agile management practices iteration planning meeting (agreed-mandate), performed iteratively, daily legislature , iterative review meetings , iterative review meeting (summary improvement)
Agile engineering practices pair programming, test-driven development, continuous integration, Code Review, product release rules, user stories
User Story three elements: customer value, user level : the epic story (January), characteristics of the story (one week), sprint story (one day), task (hours)
