Inadequate requirements specifications not understandable to users are one of predominant causes of failure in the development of software systems today. The aim is to find a technique understandable to users in order for them to be able to validate these requirements andverify whether these requirements are really what they need. On the other hand, the aim is finding the way of specifying requirements that would be in accordance with modern techniques of developing software systems such as traceability and iterative and incremental development. Use cases are a reliable technique of resolving the problems mentioned.

Abstract.

Keywords. Use cases, Use-casemodel, Requirements, Requirements specification, Requirements techniques, Traceability, Iterative, Software development, Methodologies 1. Introduction
Many studies show that one of the primary challenges of vital importance to any information system development is the ability to elicit the correct and necessary system requirements and specify them in a manner that is understandable to users in orderfor those requirements to be verified and validated [6]. The information technology community has always had problems trying to specify requirements, especially functional requirements, to users [13]. There were tendencies to produce diagrams and specifications that were loaded with terminology and notation resembling a computer code. The traditional ways of expressing functionality to users arerequirements specifications, functional decompositions, data-flow diagrams (DFDs), entity-relationship diagrams (ERDs), prototypes, etc. These modes of expressing functionality of a system are not understandable to users [7]. Traditionally, requirements are specified in lists and expressed in terms of ‘’the system shall’’. The requirements lists provide a

comprehensive catalog of every functionthat the system should perform. In most cases these lists contain duplicate or conflicting requirements. Another attempt to describe functionality of the system is functional decomposition. This method takes the major function of the system, the highest level function and breaks it down to subprocesses, and sub-subprocesses, and so on. When the processes are small enough, they become a program.Functional decomposition is a remnant of the older analysis and design approaches. It is tightly linked to structured systems development, meaning COBOL and mainframes. It is not usable for an application that is Web-based or object-oriented [7]. The world-famous methodologies, like structured techniques and information engineering, have a traditional approach to software development. Their mainartifacts for developing systems are data-flow diagrams and entity-relationship diagrams. In the design phase data-flow diagrams are sometimes called flowcharts. These methodologies are similar because there exist two parallel separated ways of developing software system. These are the process model and the data model. The main difference between the two types of methodologies is that the structuredtechniques are based on processes, i.e. the process model is their primary artifact, while information engineering is based on data, and in this approach the data model is the primary artifact [13]. Data flow diagrams help to show a system as a set of groups of interacting processes. They represent the dynamic view of the system and focus on what happens inside the system. The data flows from oneprocess to another, and then stops in a data store. Entity-relationship diagrams show how the data is stored in an application. They show details of entities, attributes, and relationships. Also, this diagram is used to present a logical data model and dictate the structure of a relational database. Both of the artifacts can be useful in the design phase primarily for non-objected software...

...The company wants to understand: why they have so small a market share; what could be done to improve the situation; where it should focus its resources.
From now on, the company studied in this case study will be referred as “client”, the buyers as libraries and the final users of the software’s (people that go to the libraries) as final users.
The McKinsey Business System Framework was used to understand the components of this business and possible solutions for the problem....

...Means Business
Approximately 80 percent of all business data are related to location. Businesses manage a world of information about sales, customers, inventory, demographic proﬁles, mailing lists, and so much more. No matter what industry you are in, business success means making wiser decisions faster than your competition. Being able to understand the market and obtain information quickly so you can take fast action is key. The intuitive power of maps often...

...Proponents of the technology claim that it does more than simply reduce costs. It allows for 'better' meetings as well: it's easier to meet with partners, suppliers, subsidiaries, and colleagues from within the office or around the world on a more frequent basis, which in most cases simply cannot be reasonably accomplished through travel. You can also meet with contacts that you wouldn't be able to meet at all without videoconferencing technology....

...United Parcel Service, the world?s largest air and ground package-distribution company, started out in 1907 in a closet-size basement office. Jim Casey and Claude Ryan?two teenagers from Seattle/>/> with two bicycles and one phone?promised the ?best service and lowest rates.? UPS has used this formula successfully for more than 90 years. Today UPS delivers more than 3 billion parcels and documents annually to the United States/>/> and to more than 200 other countries and...

Empresa

Seguir

{"essaysImgCdnUrl":"\/\/images-study.netdna-ssl.com\/pi\/","useDefaultThumbs":true,"defaultThumbImgs":["\/\/bts-study.netdna-ssl.com\/stm\/images\/placeholders\/default_paper_4.png","\/\/bts-study.netdna-ssl.com\/stm\/images\/placeholders\/default_paper_2.png","\/\/bts-study.netdna-ssl.com\/stm\/images\/placeholders\/default_paper_3.png","\/\/bts-study.netdna-ssl.com\/stm\/images\/placeholders\/default_paper_4.png","\/\/bts-study.netdna-ssl.com\/stm\/images\/placeholders\/default_paper_5.png"],"thumb_default_size":"160x220","thumb_ac_size":"80x110","isPayOrJoin":false,"essayUpload":true,"site_id":2,"autoComplete":false,"isPremiumCountry":true,"userCountryCode":"US","logPixelPath":"\/\/www.smhpix.com\/pixel.gif","tracking_url":"\/\/www.smhpix.com\/pixel.gif","cookies":{"unlimitedBanner":"off"},"essay":{"essayId":9028242,"categoryName":"Tecnología","categoryParentId":null,"currentPage":1,"format":"text","pageMeta":{"text":{"startPage":1,"endPage":16,"pageRange":"1-16","totalPages":16}},"access":"free","title":"Information systems modeling with use cases","additionalIds":[],"additional":[],"loadedPages":{"html":[],"text":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16]}},"user":null,"canonicalUrl":"http:\/\/www.buenastareas.com\/ensayos\/Information-Systems-Modeling-With-Use-Cases\/3604356.html","pagesPerLoad":50,"userType":"member_guest","ct":0,"ndocs":"11,100,000","pdocs":"","cc":"10_PERCENT_1MO_AND_6MO","signUpUrl":"https:\/\/www.buenastareas.com\/inscribirse\/","joinUrl":"https:\/\/www.buenastareas.com\/join.php","payPlanUrl":null,"upgradeUrl":"\/contribuir?newuser=1","freeTrialUrl":null,"showModal":"get-access","showModalUrl":"https:\/\/www.buenastareas.com\/inscribirse\/?redirectUrl=https%3A%2F%2Fwww.buenastareas.com%2Fjoin.php","joinFreeUrl":"\/contribuir?newuser=1","siteId":2,"facebook":{"clientId":"117783761627229","version":"v2.8","language":"es_ES"},"analytics":{"googleId":"UA-18439344-1"}}