• Save
Non-Functional Requirements Description Language
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Non-Functional Requirements Description Language

on

  • 2,121 views

 

Statistics

Views

Total Views
2,121
Views on SlideShare
2,109
Embed Views
12

Actions

Likes
1
Downloads
0
Comments
0

5 Embeds 12

http://www.slideshare.net 7
http://www.linkedin.com 2
http://www.lmodules.com 1
http://translate.googleusercontent.com 1
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Non-Functional Requirements Description Language Presentation Transcript

  • 1. Non-Functional Requirements Description Language
  • 2. Software Architecture
    • Views and Viewpoints of Architecture Blueprint
      • Functional/logic view
      • Code/module view
      • Development/structural view
      • Concurrency/process/thread view
      • Physical/deployment view
      • User action/feedback view
      • Data view
  • 3. Self-aware Challenges of SOA based Software Systems
    • Self-Adapting to Requirements changes
    • Self-Governance to Requirements, Models, Services, Processes, Components.
    • Self-Configuring of running system through system components
    • Self-Configuring to processes (hot swapping of services)
    • Self-Healing after system faults
    • Self-Discovery and Self-fixing of bugs
  • 4. Approach To Challenges
    • Models & Description Languages describing System interaction for :
      • Capturing Requirements from intentions vocabularies
      • Modeling Requirements
      • Compositing system components
      • Monitoring, Diagnosing system functions
      • Discovering system bugs, vulnerability from
      • Reasoning and knowledge of running system
  • 5. Ontology Approach
    • Ontological Annotation of Process Flow
      • This will help logic composition of processes
    • OWL-S and WSMO give an ontological formation of the axioms in software architecture (processes and web services),
    • An interface layer can be designed to map between Neptune components and WSMO
  • 6. Biomimicry Approach
    • Agent Based modeling, interaction and intelligence of System would help to give life representation to system artifacts
      • health check agents, risk control agents, quality assurance agents,..etc
  • 7. Exposed Quality & Performance Properties of the Ecosystem
    • Business Level
      • Organizational Goals, Objectives
        • Strategy, KPI’s
    • Intention Level (Human Level/Process owner level)
      • User goals
      • User inputs and outputs
    • Process Level (Business Level)
      • KPI’s
      • Performance
    • Service Level (Service Provider)
      • Reliability – MTBF
      • Availability (up-time), time-to-deliver, response-time
      • Serviceability: MTTR
      • Capacity: throughput
  • 8. NFR’s Example
    • The system shall accommodate 400 users during the peak usage time window of 8:00am to 10:00am local time, with an estimated average session duration of 8 minutes .
    • All Web pages generated by the system shall be fully downloadable in no more than 10 seconds over a 40KBps modem connection.
    • Responses to queries shall take no longer than 7 seconds to load onto the screen after the user submits the query.
    • The system shall display confirmation messages to users within 4 seconds after the user submits information to the system.
    Metrics
  • 9. Non-Functional Requirements Description Language
    • Motivations
      • To get a mutual understanding of customer NFR’s in one assembly that highlight the objects:
        • Category of NFR
        • Metrics of NFR on Activity Level inside a Process that will match SLO’s from Service Provider
      • Supports MDA/MDD agility
      • Matching criteria between NFR’s and SLO’s through Metrics Semantically
      • Monitoring and diagnosing NFR’s at deployment
      • Evaluating NFR’s on service level
  • 10. Non-Functional Requirements Description Language
    • Design Goals
      • NFR’s should embed SMART (Specific, Measurable, Attainable, Realistic, Time bound) properties
      • Simple and quantitative metric design for each NFR
      • Simple business rule annotation
      • NFR contain an object, property, metric and constraint
        • Metric contain measurement, function and criteria
      • Design should expose interfaces for viewpoints for other emerging services like diagnostic services
  • 11. Self-Governance System Axioms Sign SLA Deploy Process Deploy on BPEL Engine SLA’s NFRDL Analyzing Error Classification Construct SLA’s Classification Optimize Formal Agreement Monitoring
  • 12. SLO’s Aggregation
    • 1- B2B Agreements contain an aggregate of SLO’s to business goals through KPI’s and Metrics
  • 13. KPI Construction
    • 5- Sign formal process intention level agreement with partners (including BPEL host provider, infrastructure resource provider); this agreement links pertained SLO’s to intention Goal in high-level KPI’s
  • 14. Monitoring KPI’s
    • Start Logging and Analyzing raw data
    • 3- If any breaches arise (violation of SLO) then;