March 2013
Beginner
154 pages
4h 2m
English
Content preview from User-Centered DesignBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Appendix A. Sample Project Template
Template
Note
We refer to our template as a Software Development Life Cycle (SDLC). This does not reflect an all-encompassing SDLC. Many firms have more elaborate development processes and documentation. As with all recommendations in this book, this template should be used as a starting point that you should change to fit your needs.
Project Title
Software Development Life Cycle Project Template
Mission Statement
Software Development Life Cycle Summary
The intent of this document is to collect, define, and organize project details and requirements. The template is designed to be iterative, meaning that it will evolve over the life of the project.
The template includes the following key sections:
Project Details: These include the summary of the project. They’re designed to collect the following information:
Title: The title or codename of the project.
Description: A summary defining the objective of the project.
Stakeholders: Members who are involved with or have requested the project.
Impact Assessment: The observed or intended impact of the project deliverable: Who will be affected by this project? How many users? What business processes will be changed as a result of this project?
User Requirements: The requirements of the project, as specified by the user. The user requirements section includes a signature of agreement. As requirements evolve, many iterations of the user requirements sheet may be included.
Specifications Sheet (Functional Requirements) ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.