PDF-System Requirements

1 DJ H PSR 0 2 13 V e r 17 St a ff a n d S tud e nt V PN User Do c ume nt at i on This d o c u ment is b r o ken d o wn i n t o the f o l l o wing se c t io n s f o r y o u r c o n ven i en. Software Lifecycle Activities. Application. Domain . Objects. SubSystems . class.... class.... class.... Implementation Domain . Objects. Source. Code. Test . Cases. ? . Expressed in Terms Of. Structured By. approaches, phases and requirements discovery. Karolina . Muszyńska. Based on http://www.csun.edu/~dn58412/IS431/IS431_SP13.html. Systems Analysis vs. Systems Design. Systems Analysis Phases and Tasks. The Stute. The system will manage the day to day operations and website of Stevens’ student newspaper, The Stute.. Technologies. ASP.NET with C#. Chosen for web controls . AJAX and . Javascript. Some built in functionality with .NET, some custom created. SENG 301. Learning Objectives. By the end of this lecture, you should be able to:. Discuss several techniques for gathering requirements. Identify functional vs. non-functional requirements. Discuss the distinction between functional vs. non-functional requirements. A simple interaction design lifecycle model. Exemplifies a user-centered design approach . 2. What, how and why?. . Why bother?. Requirements definition is the stage where failure occurs most commonly. Analisis. . dan. . Perancangan. . Sistem. Goal. Define and understand the characteristics of and rules for writing good requirements.. Understand the value of providing the rationale and the preliminary verification technique with each requirement.. 1. 8/31/2016. Topics covered. Functional and non-functional requirements. Requirements engineering processes. Requirements elicitation. Requirements . specification. Requirements validation. Requirements change. Defining the Functional Needs of Our College. Strategic. Technology. Plan . 2012. 2010. 2009. 2008. 2011. . Project . Roadmap. Project Principles. Developed. Readiness. Assessment. & Detailed. Introduction. The systems development process transforms the existing (as is) system into the proposed (to be) system. Requirements determination. The single most critical step of the entire SDLC. Changes can be made easily in this stage. Lecture 1. 1. Chapter 4 Requirements engineering. Topics covered. Functional and non-functional requirements. The software requirements document . Requirements specification. Requirements engineering processes. 1. 8/31/2016. Topics covered. Functional and non-functional requirements. Requirements engineering processes. Requirements elicitation. Requirements . specification. Requirements validation. Requirements change. Software Requirements and Models 1 8/31/2016 Topics covered Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation M. KUIVANIEMI. 1. , N. MODIG. 2. , R. ERIKSSON. 2. Fingrid Oyj. 1. , Svenska kraftnät (Swedish National Grid). 2. Motivation. Reduced inertia and availability of primary reserves challenges frequency stability during severe power imbalances. 6-. 2. Objectives. Define system requirements and differentiate between functional and nonfunctional requirements. . Understand the activity of problem analysis and be able to create an Ishikawa (fishbone) diagram. .