Applied Software Project Management. Requirements. Software Requirements. Software requirements are documentation that completely describes the behavior that is required of the software-before the software is designed built and tested.
Discussion Summary outline
Teach the skills and techniques that you will need to:
A product team's primary means of communicating the design and functionality requirements of each feature in a product
An architecture spec, vision document, one-page summary, e-mail, or hallway conversation
Many challenges faced by PMs in composing an effective spec can be viewed as a lack of:
Instead of focusing on solving a technical problem, we get caught up in documenting a recipe for "code that must be written."
Gather anything you can. Talk to the customers and all disciplines, including marketing. Listen to yourself also.
This needs to be done up front, not as the spec is evolving. If you need additional research or validation as you work through the document, that is OK. Save a place for it and design the research to get the answers that you need.
You need to know, at a feature level, what the industry is offering or wanting.
Look for various alternatives and call in folks from various functional groups, as appropriate, to gather data
Decide what tools are most appropriate for the type of message you want to communicate:
Use brainstorming to tap your brain for a rush of ideas
(Sounds cool, eh?)
Clustering is an organizing technique that you can use with brainstorming
FOCUS ON AUDIENCE NEEDS
The Office Web Server supports DAV as a native protocol on non-Platinum server platforms. DAV clients implicitly get access to the rich document management services that Office Web Server provides, such as link fixup. DAV clients can also participate in the Office Web Server world by gaining access to the Office Web Server metadata store.
Office Web Server benefits because DAV is embraced and extended, and ISPs/Server Admins aren’t faced with a choice about open protocol with less functionality vs. closed protocol with rich fully integrated with office functionality. OWS gets the open standards checkbox. Implementing a DAV stack also begins the process of figuring out how to extend DAV to encompass the richness of the Office Web Server functionality.
We add support for surrogate pairs and the BOM in UTF-8, and for improving load performance on common code pages.
We’re also working with IE to have better support for half-width kana in the “Japanese (JIS)” encoding if the user has IE 6 MLANG installed.
There were a bunch of encoding issues that came up during the course of Office 2000. We’re fixing the ones that we think affect a substantial number of users.
[Easier and faster faxing] When Cheryl signed up for Office.NET, she noticed that there is a Fax service provided by Office. In the past, each time she needed to send a fax, she printed out her file, brought it to her company fax machine, and stood by the machine to monitor it as it sends her fax. Now with Office.NET, she can do all this from her computer. While logged onto Office.NET, she selects the documents she wants to fax and faxes it with just a few clicks of her mouse. She gets a confirmation in her email inbox a few minutes later, notifying her that the documents were successfully faxed.
Any time you have seen a file dialog in any custom applications. .
We covered and practiced spec'ing techniques that have proven successful at Microsoft and we learned that:
Use idea-mapping to generate ideas and identify their logical relationships