http://cs-comm.lib.muohio.edu/items/browse?tags=Requirements&output=atom<![CDATA[Incorporating Communication Outcomes into the Computer Science Curriculum]]>
The dissemination of the project's research will come with the creation of a repository that allows CSE faculty members to access a web-based set of assignments. The goal of these assignments is to aid CSE faculty in redesigning their assignments, courses, and curricula in order to incorporate and enhance their students abilities to communicate and collaborate with a wide variety of audiences. The repository will be populated with assignments written and designed by both CSE and CAC faculty with the premise of integrating communication abilities while also enhancing the learning of the technical content being taught in their course and/or curriculum.
]]>2020-05-18T19:08:43-04:00Omekahttp://cs-comm.lib.muohio.edu/items/show/93<![CDATA[Project presentations]]>2012-07-26T06:33:26-04:00
Title
Project presentations
Course
Software Engineering
Abstract
This is a set of presentation assignments for the semester-long class project. For each iteration of the project teams present their understanding of the project and demo the implementation to the client. Teams are also expected to elicit feedback from the client.
Author
Douglas Troy
Source
Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition), 2004.
Genre
Oral presentation
Assignment Duration
Short Activity
Communication Skill
Writing
Speaking
Teaming
Listening
Technical Skill
Requirements
Workplace Scenario
In this assignment your team will make an oral presentation, summarizing the results of the Inception Phase, to your client, co-workers, and supervisor. You should summarize the content of the artifacts produced in the Inception Phase (Vision, Use Case Model, Glossary, and Supplementary Specification). You should create visual aids (such as a PowerPoint deck, handouts, etc) to supplement your presentation.
The ability to present information orally to a variety of audiences is a very important skill to learn and practice. It probably goes without saying that you will be called upon in your internships and career to present information orally, but you will probably also want to make such presentations to social groups and a variety of other organizations with which you become a member.
An oral presentation is a prepared, purposeful presentation designed to increase knowledge, foster understanding, or promote change in the listeners’ attitudes, values, beliefs, or behaviors. In our case we want to foster understanding within your team, your supervisor, and the client that we have a good understanding of the project’s overall goals and scope.
This is a semester-long class project using iterative development for a sophomore-level course. Students are assumed to have had an introduction to object-oriented programming. The attached zip file has assignments for five iterations covering the inception, elaboration, and contruction phases.
Author
Douglas Troy
Source
Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition), 2004.
Genre
Report
Code
Assignment Duration
Two Weeks
Communication Skill
Writing
Teaming
Listening
Technical Skill
Requirements
Workplace Scenario
The most important step in the software development process is to understand the problem to be solved. The “problem” is typically a set of “needs” of the client related to their business or organization. If you come up with a great solution that does not meet the needs of the client, your project will not be a success!
The Vision document is one of the early documents that we create in our software development methodology. It’s our opportunity to work with the client to establish a common vision and basic scope for the project. We can explore the client’s vision for the project, its feasibility within the time and resources that we have, make a rough estimate of cost and time complete the project, and decide whether or not we can move ahead with the project. This is an essential step in any project. Note that we are not trying to completely define the client’s needs (requirements) or the solution. This will evolve as we move forward with the project.
The Supplemental Specification and the Glossary support the Vision. The focus of the vision is primarily on functional requirements (the features seen by the user). The Supplemental Specification captures the “URPS+” non-functional requirements: Usability, Reliability, Performance, Supportability and any others (such as legal issues). The Glossary defines critical terminology, and can sometimes document the format of data.
This is a team assignment to work with the client to create a common vision and scope for the class project, and to create the initial product backlog. This will help assure that your project is a success and meets the needs of the client. Note that these are “living documents” and will evolve as the project progresses.
Please note that the audience for the Vision, Supplemental Specification and Glossary includes the software engineers on your team and the client. This means that these documents should be written so that the client can easily understand them (don’t overuse technical jargon or acronyms, for example).
Team Size
4-6
]]>http://cs-comm.lib.muohio.edu/items/show/40<![CDATA[Eliciting Requirements: Use Case Modeling Memo]]>2012-07-25T21:56:50-04:00
Title
Eliciting Requirements: Use Case Modeling Memo
Course
Software Engineering
Abstract
Analyze and create a requirements specifications using scenarios or use cases.
Author
Douglas Troy
Source
Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition), 2004.
Genre
Recommendation
Memo
Assignment Duration
Less than a week
Communication Skill
Writing
Technical Skill
Requirements
Workplace Scenario
The primary tool at our disposal for defining requirements and identifying features is Use Case Modeling. Use cases are simply scenarios, or stories, that capture the functions that the system provides for the users. The use cases will help you to create your Product Backlog. In this memo to your supervisor, you will identify two use cases for your team’s part of the class project.
Team Size
N/A
]]>http://cs-comm.lib.muohio.edu/items/show/34<![CDATA[Eliciting Requirements: Preparation for Requirements Workshop with Client]]>2012-07-25T21:54:31-04:00
Title
Eliciting Requirements: Preparation for Requirements Workshop with Client
Course
Software Engineering
Abstract
Analyze and create a requirements specifications using scenarios. Prepare to interview a client.
Author
Douglas Troy
Source
Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition), 2004.
Genre
Memo
Assignment Duration
Less than a week
Communication Skill
Writing
Technical Skill
Requirements
Design
Workplace Scenario
The Inception Phase of our project is upon us! It’s our opportunity to work with the client to establish a common vision and scope for the project. We explore the client’s vision for the project, create an initial list of features (requirements), make a rough estimate of cost time needed to complete the features, and decide whether or not it is feasible to move ahead with the project given our resource (time and people) constraints. Note that in the spirit of agile, iterative development, we are not trying to completely define the client’s needs (requirements) or the solution at this time. A fuller understanding of the requirements will evolve as we move forward with the project.
We will kick off the project with a Requirements Workshop with our client in our next class meeting. Oftentimes the Software Engineer must explore the client’s vision through a dialog with the client. So for this assignment, I want you to prepare for the meeting by composing a few questions to ask the client in order for you to better understand:
• The client’s vision for the product
• The opportunity/benefits of the product that the client envisions
• The primary stakeholders, such as the “owner” of the product and the “users” of the product.
• The user-level goals: What is the vision for how the users will use the product?
• A list, of potential features of the product
• Any other requirements for the product such as usability, reliability, security, performance, etc
The information that you collect will be used to write your team’s Vision, Supplemental Specification, Use Cases, and Glossary. The features will be the basis for your teams Product Backlog.
In this memo to your supervisor, you will recommend four questions to the client that will help you to write the project vision document.