Skip to main content

Modelling Requirements -USE CASE

                                                                     Modelling Requirements

                In modelling requirements, we use different techniques for IT systems. These techniques are used to analyse and specify requirements during the developing the system according the requiremens.
                Models are very helpful to clarify ,understand and cross check the requirements. For completeness of the analysis. These models are perspective of system and users. For that purpose we use Unified Modeling Language and Entity relationship modelling(Data driven model).


Modelling system requirements
                                                            “One picture worth 10,000 words”

                      Its extremely difficult, If not impossible, to write textual statements thar are completely umambiguous.
The view of a system that is often most accessible to business users depicts the funtions that will be provided and the actors who are involved in using those functions.
                A function may be defined as a set of actions that the business users want the IT system to support in order to achieve a specific goal.
·         Accepting the details of the customer
·         Validate the details
·         Store the customer details to retrieve and filter details according to our specifications.
Unified Modelling language
                                               In UML, a use case is something that an actor wants the IT system to do; It is a Use case of the system by a specific actor and describes the interaction between the actor and the system.
Each use case has specific task and description to support the functional and non functional requirements and how user and system interacts.

                                                                         USE CASE 
          
Commonly we found in the use case diagram are
·            Actors
·            Use case
·            System Boundary
·            Associations

Actors :  Actors are the users of the system who access the functionality of the system i.e Use case of the systems.
                   Actors are 2 types
·         Primary actors : who are the directly interacting with system and access the functionality of the system
·         Secondary actors : Most of the time, Back end operators like data bases and supporting members come into this category.

Use case :
                  Is shown as an oval and represents a function that the system will perform in response to a trigger from the actor.

System boundary
                 Is indicated by drawing a large box around all of the use cases but with the actors outside the box.

Associations
              Indicate which actors will need to interact with which use cases. Lines are drawn linking actors with the appropriate use cases.

v  Generalization
                     USE case generalization
                                                                                             Actor Generalization                                        
v   INCLUDE
v   EXTEND




Comments

Post a Comment

Popular posts from this blog

Role OF BA in IT Project

Slides how BA communicates in project ensures to client: properly gathered,communicates the same with technical team in UML. Communicates with clients in Business Language. Nurtures the IT team with IT solution. Technical team heads with PM and Team Leader with in time frames. PM,take cares about the technical aspects of project. Teamleader cares about the delivery of project in defined time frames. BA continuously track of the client requirements through all different stages of PLC. Helping technical Team to understand requirements clearly and participates in UAT. Takes ownership from the client to ensure the project is completed according to the clients requirements.
Post a Comment
Read more

Creativity of ChatGPT in putting my wrong prompt into story

Today I am a little bit lazy due to the climate. In that laziness, I wrongly prompted the ChatGPT instead convert requirement into userstory and asked about my requirement for the story. My mistake turned into a beautiful story that I can explain to my team while grooming those stories in future sprints.  Prompt : convert the requirement into story Requirement:  "Show" options: Display number of records onscreen based on selection.  Options are 50 (default), 100, 150, and 250.  Pagination should adjust based on the number of records being displayed.  Disable options that are not relevant - example: if the table only has 40 records, disable the remaining options (100 150 and 250) Selection should be sticky by user within and across sessions.  Display the number of records the user has selected when they navigate away from the page and return (if they were showing 100 records when they left; show 100 records when they return) Pagination is always visible and ...
Post a Comment
Read more

Are Skill Development Missions Successful?

Skill development missions are very common in India and abroad to upscale the skills of rural and urban educated and unemployed youth. Most of the skill development missions have common agenda to create employment with proper training and providing certifications by industrial experts. It’s in positive perspective. Do you think, is it helpful to uproot and groom the skills to create employment with few interactive sessions with industrial experts? There are lot of gaps in those missions. All the missions and objectives are time bound and no one have the accountability in creation of jobs except training. After training we need to put into test in real time and need to gather continues feedback from the attendees. And capture the information with proper questionnaire instead of ‘yes’ or ‘no’ questionnaire which can’t provide proper feedback to understand the attendee’s opinions. Feedback System Feedback system must be very strong and follow ups with attendees must be frequ...
Post a Comment
Read more