欢迎来到麦多课文档分享! | 帮助中心 海量文档,免费浏览,给你所需,享你所想!
麦多课文档分享
全部分类
  • 标准规范>
  • 教学课件>
  • 考试资料>
  • 办公文档>
  • 学术论文>
  • 行业资料>
  • 易语言源码>
  • ImageVerifierCode 换一换
    首页 麦多课文档分享 > 资源分类 > PPT文档下载
    分享到微信 分享到微博 分享到QQ空间

    System RequirementsSpecification.ppt

    • 资源ID:389560       资源大小:359KB        全文页数:24页
    • 资源格式: PPT        下载积分:2000积分
    快捷下载 游客一键下载
    账号登录下载
    微信登录下载
    二维码
    微信扫一扫登录
    下载资源需要2000积分(如需开发票,请勿充值!)
    邮箱/手机:
    温馨提示:
    如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
    如需开发票,请勿充值!如填写123,账号就是123,密码也是123。
    支付方式: 支付宝扫码支付    微信扫码支付   
    验证码:   换一换

    加入VIP,交流精品资源
     
    账号:
    密码:
    验证码:   换一换
      忘记密码?
        
    友情提示
    2、PDF文件下载后,可能会被浏览器默认打开,此种情况可以点击浏览器菜单,保存网页到桌面,就可以正常下载了。
    3、本站不支持迅雷下载,请使用电脑自带的IE浏览器,或者360浏览器、谷歌浏览器下载即可。
    4、本站资源下载后的文档和图纸-无水印,预览文档经过压缩,下载后原文更清晰。
    5、试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。

    System RequirementsSpecification.ppt

    1、System Requirements Specification,Specifying the Specifications,Review from last class,Requirements Engineering Tasks Inception Elicitation Elaboration - next brief topic Negotiation Specification - main topic tonight Validation Management,Modeling,What are the benefits of building a model?So, what

    2、needs to be modeled?,System Modeling,Function & Information Flow Model what we will do with the data Data Model structure of the information Behavior Model how we interact with the system,Functional and Information Flow Modeling,Data Flow Diagrams,compiler,source code,object code,characters,machine

    3、instructions,Syntax Analysis,characters,Semantic Analysis,tokens,yadda yadda,machine instructions,DFDs also require a Data Dictionary,Data Modeling,Data Objects, Attributes, Relationships Formatted as Lists or TablesEntity Relationship Diagrams,Behavior Modeling,State Transition Diagram,1,3,2,4,star

    4、t,read msg,save msg,file name,done,compose,send,Combining Info Flow & Behavior,Use Cases,http:/ Engineering Tasks Inception Elicitation Elaboration Negotiation Specification Validation Management,Technically Speaking, “requirement“ “specification“,Requirement understanding between customer and suppl

    5、ier Specification what the software must do Requirements that are not in the SRS Costs Delivery dates Acceptance procedures etc,Uses of the SRS,Design Validation Customer Contract rarely,IEEE 830,Role of SRS “The SRS must correctly define all of the software requirements, but no more.” “The SRS shou

    6、ld not describe design, verification, or project management details, except for required design constraints.”,IEEE 830,Characteristics of a Good SRS Unambiguous Complete Verifiable Consistent Modifiable Traceable Usable during the Operation and Maintenance Phase,Desired SRS Characteristics,CompleteC

    7、onsistentChangeableTraceable,Ambiguousness example one,The control total is taken from the last record.The total is taken from the record at the end of the file. The total is taken from the latest record. The total is taken from the previous record.,IEEE 830,Ambiguousness example two,All customers h

    8、ave the same control field.All customers have the same value in their control field. All control fields have the same format. One control field is issued for all customers.,IEEE 830,Ambiguousness example three,When a user fails to authenticate after a number of times, send a notification to IT.,http

    9、:/ Complete,Unclear,The system shall be able to read updates from MedImgThe system shall be able to provide historical reports,Clearer,The system shall be able to import new tumor patient data supplied by MedImg to the radiology management system, for evaluating the tumor to be malignant or benign T

    10、he system shall be able to provide patient tumor data for the past five calendar years,http:/ Requirements,Through input/output specs aka IEEE 830 FormatUse of Representative ExamplesSpecification through Models,IEEE 830,SRS Table of Contents,Introduction Purpose Scope Definitions References Overvie

    11、w General Description Product Perspective Product Functions User Characteristics General Constraints Assumptions and Dependencies Specific Requirements,IEEE 830,3. Specific Requirements3.1 Functional Requirements3.1.1 Func Req 13.1.1.1 Introduction3.1.1.2 Inputs3.1.1.3 Processing3.1.1.4 Outputs3.1.2

    12、 Func Req 23.2 External Interface Requirements3.2.1 User Interface3.2.2 Hardware Interfaces3.2.3 Software Interfaces3.2.4 Communication Interfaces3.3 Performance Requirements3.4 Design Constraints3.4.1 Standards Compliance3.4.2 Hardware Limitations3.5 Attributes3.5.1 Security3.5.2 Maintainability3.6

    13、 Other Requirements3.6.1 Database,IEEE 830,Non-830-Style Requirements,User stories encourage the team to defer collecting details. An initial place-holding goal-level story (“A Recruiter can post a new job opening“) can be written and then replaced with more detailed stories once it becomes importan

    14、t to have the details. This technique makes user stories perfect for time-constrained projects. A team can very quickly write a few dozen stories to give them an overall feel for the system. They can then plunge into the details on a few of the stories and can be coding much sooner than a team that

    15、feels compelled to complete an IEEE 830style software requirements specification.,Quote from “Advantages of User Stories for Requirements“ By Mike Cohn http:/ Specification Techniques,Use Cases Formal Specification Languages e.g. Petri Nets,http:/www.cs.indiana.edu/classes/p465/Lect/Images/petri-img-10.jpg,Next Classes,Agile Development Risk Analysis and Management Metrics Managing the Testing Process,


    注意事项

    本文(System RequirementsSpecification.ppt)为本站会员(proposalcash356)主动上传,麦多课文档分享仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文档分享(点击联系客服),我们立即给予删除!




    关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

    copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
    备案/许可证编号:苏ICP备17064731号-1 

    收起
    展开