Sprint 3 CSCI 420 Software Engineering Development Goals
Explore the development goals of Sprint 3 in CSCI 420 software engineering, including learning more about testing with coverage requirements, working better as a team, reflecting on Sprint 2 accomplishments, and discussing improvement strategies. Dive into requirements modeling and visibility of members, and understand the model and view requirements for relationships in software engineering.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Sprint 3 CSCI 420: SOFTWARE ENGINEERING
Keep the user happy Development Goals Learn more Testing with coverage requirements
Work better as a team Meta-Goals Better user stories Better decomposition of tasks
Looking Back on Sprint 2 What did you do well? What didn t you do well? Accomplishments Achievements Hard Problems Solved Cohesion, Working Well Together How can you improve? What could/would you change? An open discussion
Requirements Model: Categories for Relationships Relationship Quantifiers Visibility of Members State (variables) vs Behavior (functions) View: Scrollable GUI View Draggable Classboxes Automatic Classbox sizing Discern/specify relationship category/quants. Relationship arrows/paths should go around other classes. Equally-functional GUI and Console All functionality present in GUI and Console One is NOT more powerful than the other Resolve Any Outstanding Bugs
Model Requirements (1/2) Categories for Relationships Aggregation (has-a, weak) open diamond, solid line Composition (has-a, strong) closed diamond, solid line Generalization (is-a) closed arrow, solid line Realization (implementation) closed arrow, dashed line See: UML Modeling Relationship quantifiers (one:one, one:many, many:one, many:many) GUI: Rendering of text along the relationship Console: your choice on how to convey this
Model Requirements (2/2) Visibility of Members: Public vs. Private vs. Protected State vs. Behavior State: All variables should have Types When an existing type is specified, a relationship should automatically be made Behavior: All functions should have a (potentially void) return type All functions should have a (potentially empty) parameter list
View Requirements (1/2) Scrollable GUI View The user should never be able to lose a classbox Draggable Classboxes Clicking and dragging on a classbox will move the classblock NOTE: It must not jump it must be an exact, per-pixel move Automatic Classbox Sizing No classboxes shall hide any content. The height/width should dynamically resize based on content Relationship arrows/lines should automatically be updated (hint: Observer)
View Requirements (2/2) Discern/specify relationship category/quantifications There should be a way to view/edit the relationship category (and if appropriate, quantification) from the console and GUI Relationship arrows/paths should go around other classes. Oof owie ouch my brain This is the hardest task. Must consider the entire environment when routing Idea: Model a path Make the path drawable Define/come up with an algorithm
Bugs your customer may have mentioned Bugs you may have found Resolve Any Outstanding Bugs Bugs you will find along the way REPORT ALL BUGS AS ISSUES
Project Manager Requirements More Pair Programming More Time Tracking (comment on issues) Add Test Coverage to Continuous Integration
Communication is key Group/team cohesion Professor Requirements Use Slack effectively Don t be too proud to ask for help Humility, Respect, Trust
