1 / 23

CS427: Software Engineering I

CS427: Software Engineering I. Darko Marinov (slides from Ralph Johnson). Administrative info. Wiki down again  If you were affected, you can submit HW5 on Thursday, Dec 7 Schedule demo between today and 18? The sooner the better Final report due on Dec 7 or by arrangement

toby
Download Presentation

CS427: Software Engineering I

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS427:Software Engineering I Darko Marinov (slides from Ralph Johnson)

  2. Administrative info • Wiki down again  • If you were affected, you can submit HW5 on Thursday, Dec 7 • Schedule demo between today and 18? • The sooner the better • Final report due on Dec 7 or by arrangement • All team members should be present or be able to explain work of the missing members • Default: Everyone on team gets the same grade for the project, BUT there can be variance CS427

  3. Final exam • Thu, Dec 14, 7-10pm • 1310 DCL • 269 Everitt • Conflict exam: Mon, Dec 11, 1:30-4:30pm • 3403 SC • More info will be on Wiki CS427

  4. Topics since midterm • Specifications • Design • Quality assurance • User interface • Two more processes • Open source (previous lecture) • Crystal clear (today) CS427

  5. Crystal clear • Reading for this lecture • Crystal light methods overview http://alistair.cockburn.us/index.php/Crystal_light_methods • A family of processes • Named after crystal terminology • Color and hardness • Crystal Clear: The Simplest Process That Can Work (Applied anthropology) CS427

  6. Crystal clear • “Good, small teams have been putting out good software for decades, using thinking, communicating and delivering as their primary tools.” • “Good, small teams do not scale up in number, so keep them small, permit them to move fast, do project tracking through their final results, not their intermediate thinking.” CS427

  7. Crystal clear assumptions • People are good at looking around • People are not as tidy as abstractions of them make them appear • Communication involves a lot more than the words spoken or written • Software construction is growing understanding of problem and solution CS427

  8. Crystal Clear assumptions • Actual, working processes are • Extremely complicated • Hard to write down • Hard to follow • Likely to be wrong when written down • Methodologists are prone to overcomplicate or embellish things CS427

  9. Crystal Clear • Make process as simple as you can • Rely on communication, individual skill • Size: 4-6 • Essential moneys, but not life CS427

  10. People • Sponsor • Senior designer • User • Designers CS427

  11. Other roles • Can be separate people, or can be one of the designers, perhaps the senior designer • Business expert • Coordinator • Tester • Writer CS427

  12. Policies • Use increments for project staging, tracking by milestones and predicted risks • Involve user directly • Requirements are annotated usage scenarios • Peer code reviews CS427

  13. Policies • Code ownership model • Regression testing framework • Code standard • User interface standard CS427

  14. Work products • Not a substitute for understanding • Understanding is primary • Work products are secondary • A substitute for discipline • A “minimal set” CS427

  15. Work products • Methodology • Team structure • Release sequence • Viewing and release schedule • Risk list • Project status CS427

  16. Requirements work products • Mission statement • Actor-goal pairs • Annotated use cases • Requirements file CS427

  17. Design work products • System design • Common object model • Screen drafts • Design sketches • Source code • Migration code CS427

  18. Tests and final system • Test cases • Test results • Packaged system • User manual CS427

  19. Making it work • How do you make sure people communicate? • How do you decide on an ownership model, coding standard, etc? CS427

  20. Requirements • Where do requirements come from? • How are they recorded? • How are they validated? • How are they used? CS427

  21. Common object model • How is the object model recorded? • How is the object model created? • How is the object model used? CS427

  22. Summary • Is XP just a special case of Crystal Light? • Could a RUP project also be a Crystal Light project? • Could a Bazaar project be a special case of Crystal Light? CS427

  23. Next: Course summary • Last lecture on Thursday, Dec 7 CS427

More Related