DOC PREVIEW
CORNELL CS 501 - CS 501 Lecture 3

This preview shows page 1-2-3-25-26-27 out of 27 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 27 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 27 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 27 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 27 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 27 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 27 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 27 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CS 501: Software Engineering Fall 2000AdministrationFeasibility StudySlide 4CS 501: ClientScopePotential BenefitsResourcesObstaclesHow to Minimize Risk?Feasibility ReportRequirements Definition and AnalysisExample: Library of Congress (A Partial Failure)ChronologyThe RepositoryStorage and Representation of Complex ObjectsRepository: Research AchievementsGood Discoveries During PrototypeBad Discoveries During PrototypeMistakesThe Requirements ProcessRequirements DefinitionLibrary of Congress Requirements StudyFunctional RequirementsPowerPoint PresentationNon-functional RequirementsEvolution of RequirementsCS 501: Software EngineeringFall 2000Lecture 3(a) Feasibility Study(b) Requirements DefinitionAdministrationAssignment 1: Look on the course web siteProject teams: • If you have definitely chosen a project, please notify the Teaching Assistants with the names of your team members• If you do not have a team you can meet after class• Monday's recitations session will be to help the people who do not have projects form teams• We may ask teams to add extra members• A Teaching Assistant will be added to each team.Feasibility StudyBefore beginning a project, a short, low-cost study to identify • Client• Scope• Potential benefits• Resources needed:staff, time, equipment, etc.• Potential obstaclesWhere are the risks? How can they be minimized?Feasibility StudyA feasibility study leads to a decision:go aheaddo not go aheadthink againIn production projects, the feasibility study often leads to a budget request.In research, a feasibility study is often in the form of a proposal.CS 501: ClientIn CS 501, you have two clients:• The client for the project• The professor for the courseCan you satisfy them both?ScopeWhat are the boundaries of the project?CS 501 Examples:• Static web pages with open access on the Web [Web Profiler]• Used by the general public [Digital Collections]• Varying data formats [Legal Information]• Thousands of sensors [Data mining]• Support for Windows, Mac, Unix [SALSA]Potential BenefitsWhy are you doing this project?Examples • Create a marketable product• Improve the efficiency of an organization• Control a system that is too complex to control manually• New or improved service• Safety or security• Get a good grade on CS 501ResourcesExamples: CS 501Staff: 5 to 7 students, with some help. How many hours per week? What skills do people have?Time: Must be completed by end of semester, including operational system, documentation, presentationEquipment and software: What special needs are there?Client: Will the client be sufficiently available and helpful?ObstaclesCS 501 projectsStart-up time. Creating a team, scheduling meetings, acquiring software, learning new systems, ...Business considerations. Licenses, trade-secrets, ...Too ambitious. Nothing to show at the end of the semester.Changing circumstances. Client leaves the university, ...What else?How to Minimize Risk?CS 501 Projects• Several target levels of functionality: required, desirable, optional• Visible software process: intermediate deliverables• Good communication within team and with Teaching AssistantGood processes lead to good softwareGood processes reduce riskFeasibility ReportA written document• For a general audience: client, financial management, technical management, etc.• Short enough that everybody reads it• Long enough that no important topics are skippedIn CS 501, I am looking for a well written, well presented document.Requirements Definition and AnalysisRequirementsDefinitionSystem andSoftware designProgrammingand Unit TestingIntegration andSystem TestingOperation andMaintenanceExample: Library of Congress(A Partial Failure)Outline DescriptionThe Library of Congress requires a repository system to store and make accessible very large amounts of highly varied material over long periods of time.Chronology 1993-94 CNRI carries out research on architectures for digital libraries1995-97 CNRI implements prototype repository for Library of Congress1998 CNRI and Library of Congress carry out requirements definitionRepositoryIdentification SystemSearch SystemUsersThe RepositoryStorage and Representation of Complex ObjectsDataSeveral representations: thumbnail image reference image archival imageMetadataEach representation may have its own metadataRepository: Research Achievements1. CORBA implementation of repository access protocol.2. Integration of persistent naming through handle system.3. Use of structural metadata to describe complex objects, elementary typology.4. Access management framework and implementation.5. Applet-based middleware for user interfaces.6. Information visualization program to view the structure of large collections.Good Discoveries During Prototype• Structuring complex information in digital libraries• Data driven digital library interfaces• Comparison of object-oriented, relational, and file based storage systems• Naming and identification of library objects• Boundaries of required repository systemBad Discoveries During Prototype• Resistance to change within Library of Congress• Technical weakness of Library of Congress• Gaps in CNRI architectureMistakes• Confusion of objectives (research and implementation)• Failure to involve all stakeholders• Over-ambitious (no proper feasibility study)The Requirements ProcessFeasibilityStudyRequirementsAnalysisRequirementsDefinitionRequirementsSpecificationFeasibilityReportSystemModelsDefinition ofRequirementsSpecification ofRequirementsRequirementsDocumentRequirements DefinitionHigh-level abstract description of requirements:• Specifies external system behavior• Comprehensible by customer, management and usersShould reflect accurately what the customer wants:• Services that the system will provide• Constraints under which it will operateLibrary of Congress Requirements StudyTeam (all experienced): Librarian, Software Engineer (CNRI), Computing Project Leader (Library of Congress), + 2 othersAdvisors: Mailing list of about 20 knowledgeable stakeholders.Timetable: Preliminary report (2 months). Final report (1 month).Functional RequirementsExample: Library of Congress repository• Support for complex digital objects•


View Full Document

CORNELL CS 501 - CS 501 Lecture 3

Documents in this Course
Quiz 2

Quiz 2

2 pages

Usability

Usability

31 pages

Quiz 1

Quiz 1

2 pages

Stulba;''

Stulba;''

33 pages

Load more
Download CS 501 Lecture 3
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view CS 501 Lecture 3 and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view CS 501 Lecture 3 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?