In object oriented analysis and design, use cases represent the things of value that the system performs for its actors in UML and unified process. Use cases are not functions or features.
They allow us to get behavioral abstraction of the system to be. The purpose of the behavioral abstraction is to get to the heart of what a system must do, we must first focus on who (or what)
will use it, or be used by it. After we do this, we look at what the system must do for those users in order to do something useful. That is what exactly we expect from the use cases as the
behavioral abstraction. Apart from this fact use cases are the poor candidates for the data abstraction. Rather the do not have data abstraction. The main reason is it shows or describes
the sequence of events or actions performed by the actor or use case, it does not take data in to account. As we know in earlier stages of the development we believe in ‘what’ rather than
‘how’. ‘What’ does not need to include data whereas ‘how’ depicts the data. As use case moves around ‘what’ only we are not able to extract the data. So in order to incorporate data in use cases one must feel the need of data at the initial stages of the development. We have developed the technique to integrate data in to the uses cases. This paper is regarding our investigations to take care of data during early stages of the software development. The collected abstraction of data helps in the analysis and then assist in forming the attributes of the candidate classes. This makes sure that we will not miss any attribute that is required in the abstracted behavior using use cases. Formalization adds to the accuracy of the data abstraction. We have investigated object constraint language to perform better data abstraction during analysis & design in unified paradigm. In this paper we have presented our research regarding early stage data abstraction and its formalization.
The document discusses the Unified Approach (UA) methodology for software development proposed by Ali Bahrami. The UA aims to combine the best practices of other methodologies like Booch, Rumbaugh, and Jacobson while using the Unified Modeling Language (UML). The core of the UA is use case-driven development. It establishes a unified framework around these methodologies using UML for modeling and documenting the software development process. The UA allows for iterative development by allowing moving between analysis, design, and modeling phases.
The document discusses various techniques for modeling software requirements including:
1) Entity-relationship diagrams (ERDs) which model data objects and their relationships to understand the data domain.
2) Use case modeling which describes scenarios of how external actors will use the system through use cases and diagrams.
3) Object-oriented modeling which defines classes, objects, attributes, methods, encapsulation, and inheritance.
4) Flow modeling using data flow diagrams (DFDs) which represent how data objects flow through the system as they are transformed.
Course material from my Object-Oriented Development course.This presentation covers the analysis phases and focuses on class discovery, domain modeling, activity diagrams, and sequence diagrams.
The document discusses functional modeling using activity diagrams and use cases. It provides guidelines for creating activity diagrams and use cases, including identifying activities, control flows, decisions, and parallel processes for activity diagrams. It also discusses writing use case descriptions in SVDPI form from an observer perspective and creating use case diagrams by connecting actors to use cases. The overall purpose is to understand and create functional models to document requirements and describe business processes.
Introduction to Object orientation , Modeling as a Design Technique Modeling ...DhwaniDesai21
This document provides an overview of object-oriented modeling concepts including the class model, state model, and interaction model. It discusses modeling as a design technique and introduces key concepts like abstraction. It then describes the three models in more detail providing examples of each. The class model represents static structure, the state model represents dynamic behavior over time, and the interaction model represents collaboration between objects.
This document describes a web application that can automatically generate Entity Relationship (ER) diagrams. It takes entity, attribute, and relationship details as input from the user and outputs an ER diagram. The proposed system has a 3-module architecture: 1) it accepts input from the user, 2) generates the ER diagram automatically based on the input, and 3) stores the output diagram. Experimental results demonstrate how diagrams are generated at different levels of complexity based on filtering of the input details. The automated generation of ER diagrams using this web application makes the process easier for users compared to traditional manual tools.
A&D - Object Oriented Analysis using UMLvinay arora
This document discusses object oriented analysis using UML. It defines key concepts like objects, classes, attributes, behaviors, generalization/specialization, aggregation, and relationships. It also describes UML diagrams including use case diagrams, class diagrams, sequence diagrams, and activity diagrams. Finally, it outlines the process of object modeling including identifying objects and classes, organizing relationships, and constructing class diagrams.
This document presents a framework for automatically generating entity-relationship (ER) diagrams from natural language text input. It involves five main modules: 1) text preprocessing and summary generation, 2) translating the summary to a Semantic Business Vocabulary and Rules (SBVR) format, 3) part-of-speech tagging, 4) extracting ER diagram requirements by identifying entities, relationships, and attributes, and 5) generating an XMI file that can be imported into a UML modeling tool to visualize the generated ER diagram. Keywords are extracted from the input text using term frequency, and sentences are scored and selected for the summary based on important keywords and nouns. The framework aims to reduce the complexity of manually creating ER diagrams by
The document provides information about UML (Unified Modeling Language), including its goals, why it is used, and common diagram types. UML is a standard language for specifying, constructing, and documenting software systems and business processes. It uses mainly graphical notations to express the design of software projects. Common UML diagram types include use case diagrams, class diagrams, interaction diagrams, state diagrams, activity diagrams, component diagrams, and deployment diagrams. Each diagram type shows different aspects of a system and allows developers and customers to view it from different perspectives.
Rumbaugh's Object Modeling Technique (OMT) is an object-oriented analysis and design methodology. It uses three main modeling approaches: object models, dynamic models, and functional models. The object model defines the structure of objects in the system through class diagrams. The dynamic model describes object behavior over time using state diagrams and event flow diagrams. The functional model represents system processes and data flow using data flow diagrams.
Lab 3 Introduction to the UML - how to create a use case diagramFarah Ahmed
The document discusses use case diagrams and use case modeling. It provides an overview of use case diagrams, including their purpose and components. Key points include:
- Use case diagrams show interactions between actors and the system/software being modeled through use cases. They are used early in development to capture requirements and later to specify system behavior.
- Components of a use case diagram include actors, use cases, and relationships between them like generalization, include, and extend. Actors represent roles that interact with the system while use cases represent system functions/processes.
- Examples of a use case diagram for a vehicle sales system are provided to demonstrate how actors, use cases, and relationships can be modeled visually. Guidance is
A Comparison of Traditional Simulation and MSAL (6-3-2015)Bob Garrett
This document compares traditional simulation approaches to the Model-Simulation-Analysis-Looping (MSAL) approach. It provides background information on system modeling and simulation basics, including conceptual models, simulation programs, sensitivity analysis, Monte Carlo methods, and simulation optimization. It then discusses risk and uncertainty, modeling systems of systems, and the current state of modeling and simulation in systems engineering. Finally, it introduces the MSAL approach, which uses graphs, analytics, and repeated simulation loops to address the increased complexity and uncertainty in systems of systems compared to traditional approaches. The MSAL approach aims to provide benefits like improved handling of uncertainty and complexity.
In this lesson, you will develop a system using Use Cases.
You will:
Justify the need for a Use Case diagram
Identify and describe the essential elements in a UML Use Case diagram
Identifying the Actors in a System.
Identifying Use Cases in a System
Create a Use Case Diagram that shows the Use Cases in your system.
Recognize and document use case dependencies using UML notation for extends,includes, and generalization
This document provides an overview of object-oriented analysis and design. It discusses traditional software development approaches versus object-oriented approaches. The key aspects of object-oriented development covered include objects, classes, inheritance, encapsulation, and polymorphism. Software development life cycle stages like planning, analysis, design, implementation and testing are also summarized. The document compares structured and object-oriented approaches and provides examples of object-oriented programming and design methodologies.
The document discusses software architecture, including definitions, principles, patterns, and modeling techniques. It defines architecture as the structure of a system comprising software elements and relationships. Some key principles discussed are single responsibility, open/closed, and dependency inversion. Common patterns like MVC, layered, and multitier architectures are explained. The document also introduces Unified Modeling Language (UML) for modeling systems using diagrams like class, component, and package diagrams.
Object Oriented Methodology (OOM) is a system development approach encouraging and facilitating re-use of software components. We enforce our concern on components re-usability of existing component using Java Language .
The document discusses different types of system models used in requirements engineering including context models, behavioral models, data models, and object models. It describes modeling the system's behavior using data flow diagrams and state machine diagrams. The document also introduces the Unified Modeling Language (UML) and how computer-aided software engineering (CASE) tools can support system modeling.
Object-oriented analysis and design (OOAD) uses visual modeling techniques like the Unified Modeling Language (UML) to analyze and design systems based on interacting objects. UML captures system elements and facilitates specification and visualization. It includes static diagrams for non-changing characteristics and dynamic diagrams for changing behaviors. The goal of OOAD and UML is to integrate analysis and development teams through defined processes and modeling.
The document discusses object-oriented design and analysis. It covers key aspects of the design phase including identifying classes, class responsibilities, and relationships between classes. The purposes of the design phase are to gather information for implementation, reduce implementation time and cost, and be the most time-consuming phase. Results of design include text descriptions and diagrams depicting relationships, usage scenarios, and state changes. The document also discusses translating analysis concepts into design, including understanding quality attributes, constraints, and requirements.
The document discusses various phases of the software development life cycle (SDLC) including analysis, design, coding, and testing.
In the analysis phase, it discusses software requirements specifications, business analysts, and their roles in initiating projects, elaborating details, and supporting implementation.
The design phase covers use case diagrams, data flow diagrams, sequence diagrams, and class diagrams. It provides examples of how to draw and use each type of diagram.
Coding involves programming languages like Java. Testing discusses the JUnit testing framework and Selenium, an open source web testing tool, covering their features and why Selenium is commonly used for automated testing.
The document discusses various phases of the software development life cycle (SDLC) including analysis, design, coding, and testing.
In the analysis phase, it discusses software requirements specifications, business analysts, and their roles in initiating projects, elaborating details, and supporting implementation.
The design phase covers use case diagrams, data flow diagrams, sequence diagrams, and class diagrams. It provides examples of how to draw and use each type of diagram.
Coding involves programming languages like Java. Testing discusses the JUnit testing framework and Selenium, an open source web testing tool, covering their features and why Selenium is commonly used for automated testing.
This document provides an overview of the contents of a textbook on object-oriented analysis and design (OOAD). It covers 6 units:
1. Object-oriented concepts, modeling, and the Unified Modeling Language (UML)
2. Iterative development and UML
3. Basic and advanced structural modeling
4. Interaction modeling
5. Architectural modeling
6. Object-oriented programming styles
The first unit introduces object-oriented paradigms and modeling techniques like the data flow diagram, entity relationship diagram, algorithms, and flowcharts. It also discusses object-oriented modeling and the process of object-oriented analysis and design.
Object-oriented analysis and design (OOAD) uses visual modeling techniques like the Unified Modeling Language (UML) to analyze and design systems based on interacting objects. UML captures system elements and facilitates specification and visualization. It includes static diagrams for non-changing characteristics and dynamic diagrams for changing behaviors. The goal of OOAD and UML is to integrate analysis and development teams through defined processes and modeling.
This document provides an overview of object oriented analysis and design using the Unified Modeling Language (UML). It discusses key concepts in object oriented programming like classes, objects, encapsulation, inheritance and polymorphism. It also outlines the software development lifecycle and phases like requirements analysis, design, coding, testing and maintenance. Finally, it introduces UML and explains how use case diagrams can be used to model the user view of a system by defining actors and use cases.
The document discusses object-oriented databases (OODBs). It states that choosing the right OODB architecture is crucial for performance and scalability, more so than with relational databases. With OODBs, the application architecture has a greater impact on performance compared to relational databases, as OODBs provide more direct access to persistent data. Consequently, the application architecture affects performance and scalability more than the choice of OODB.
This document discusses various UML diagrams including class diagrams, use case diagrams, and their advantages and disadvantages. It provides an example class diagram for the abstract factory design pattern. Use case diagrams are used to gather system requirements and show interactions between actors and use cases. They provide an outside view of a system and can be used in both forward and reverse engineering. While useful for requirements analysis, use case diagrams do not describe implementation details.
The document provides an overview of the core concepts and processes involved in systems analysis and design using a running example project from beginning to end. It introduces the systems development life cycle (SDLC) as consisting of six core processes: (1) identifying needs and obtaining approval, (2) planning and monitoring the project, (3) defining requirements, (4) designing solutions, (5) building and testing solutions, and (6) launching solutions. The chapter then discusses these six core processes that are common to all types of SDLC approaches.
1-SDLC - Development Models – Waterfall, Rapid Application Development, Agile...JOHNLEAK1
This document provides information about different types of data models:
1. Conceptual data models define entities, attributes, and relationships at a high level without technical details.
2. Logical data models build on conceptual models by adding more detail like data types but remain independent of specific databases.
3. Physical data models describe how the database will be implemented for a specific database system, including keys, constraints and other features.
The document provides information on Unified Modeling Language (UML) and its various diagrams used for modeling software systems. It discusses the background and benefits of object-oriented modeling. It then describes UML as a modeling language comprising various diagram types to capture different views of a system, including structural, behavioral, implementation and user views. Specific diagram types covered include use case diagrams, class diagrams, sequence diagrams, and object diagrams. Examples are provided for each diagram type to illustrate their elements and notation.
Software Engineering Tools and Practices.pdfMeagGhn
This document discusses software engineering practices and tools, including the software crisis and issues like increasing complexity, poor quality, high costs and delays. It introduces Unified Modeling Language (UML) as a standard way to visually model software systems using diagrams. It describes different types of UML models including structural, behavioral and architectural modeling. It also discusses concepts like the software development life cycle, configuration management, revision control systems and how to create UML diagrams like use case diagrams and sequence diagrams.
This document provides an introduction to object-oriented analysis and design (OOAD) and the Unified Modeling Language (UML). It discusses the basic concepts of OOAD and how UML uses diagrams to model software systems. UML diagrams can be used in all phases of the software development life cycle, including requirements analysis, design, implementation, and testing. The document also gives an overview of the different parts of UML, such as views, diagrams, relationships, and model elements.
This document provides an overview of topics covered in Chapter 7 on software design and implementation, including object-oriented design using UML, design patterns, implementation issues, and open source development. It discusses the design and implementation process, build vs buy approaches, object-oriented design processes involving system models, and key activities like defining system context, identifying objects and interfaces. Specific examples are provided for designing a wilderness weather station system.
The document discusses analysis modeling principles and techniques used in requirements analysis. It covers key topics such as:
1. The purpose of requirements analysis is to specify a software system's operational characteristics, interface with other systems, and constraints. Models are built to depict user scenarios, functions, problem classes, system behavior, and data flow.
2. Analysis modeling follows principles such as representing the information domain, defining functions, modeling behavior, partitioning models, and moving from essential to implementation details. Common techniques include use case modeling, class modeling, data flow diagrams, state diagrams, and CRC modeling.
3. The objectives of analysis modeling are to describe customer requirements, establish a basis for software design, and define a set
The document discusses requirements analysis and analysis modeling principles for software engineering. It covers key topics such as:
1. Requirements analysis specifies a software's operational characteristics and interface with other systems to establish constraints. Analysis modeling focuses on what the software needs to do, not how it will be implemented.
2. Analysis modeling principles include representing the information domain, defining functions, modeling behavior, partitioning complex problems, and moving from essential information to implementation details.
3. Common analysis techniques involve use case diagrams, class diagrams, state diagrams, data flow diagrams, and data modeling to define attributes, relationships, cardinality and modality between data objects.
Data modeling is the process of creating a visual representation of data within an information system to illustrate the relationships between different data types and structures. The goal is to model data at conceptual, logical, and physical levels to support business needs and requirements. Conceptual models provide an overview of key entities and relationships, logical models add greater detail, and physical models specify how data will be stored in databases. Data modeling benefits include reduced errors, improved communication and performance, and easier management of data mapping.
Quality Assurance. Quality Assurance Approach. White BoxKimberly Jones
The document discusses using the Unified Modeling Language (UML) to model database systems and computer applications. It describes how UML diagrams like use case diagrams, class diagrams, sequence diagrams, and deployment diagrams can be used at different stages of the software development process. The paper examines how these UML diagrams integrate with various programming methodologies and how they provide a standardized way to visually define and model the design and structure of software systems, including defining objects in an object-oriented design approach.
Object Oriented Methodologies discusses several object-oriented analysis and design methodologies including Rambaugh's Object Modeling Technique (OMT), Booch methodology, and Jacobson's Object-Oriented Software Engineering (OOSE). OMT separates modeling into object, dynamic, and functional models represented by diagrams. Booch methodology uses class, object, state transition, module, process, and interaction diagrams. OOSE includes use case, domain object, analysis object, implementation, and test models.
Similar to FORMALIZATION & DATA ABSTRACTION DURING USE CASE MODELING IN OBJECT ORIENTED ANALYSIS & DESIGN (20)
ANALYSIS OF LAND SURFACE DEFORMATION GRADIENT BY DINSAR cscpconf
The progressive development of Synthetic Aperture Radar (SAR) systems diversify the exploitation of the generated images by these systems in different applications of geoscience. Detection and monitoring surface deformations, procreated by various phenomena had benefited from this evolution and had been realized by interferometry (InSAR) and differential interferometry (DInSAR) techniques. Nevertheless, spatial and temporal decorrelations of the interferometric couples used, limit strongly the precision of analysis results by these techniques. In this context, we propose, in this work, a methodological approach of surface deformation detection and analysis by differential interferograms to show the limits of this technique according to noise quality and level. The detectability model is generated from the deformation signatures, by simulating a linear fault merged to the images couples of ERS1 / ERS2 sensors acquired in a region of the Algerian south.
4D AUTOMATIC LIP-READING FOR SPEAKER'S FACE IDENTIFCATIONcscpconf
A novel based a trajectory-guided, concatenating approach for synthesizing high-quality image real sample renders video is proposed . The lips reading automated is seeking for modeled the closest real image sample sequence preserve in the library under the data video to the HMM predicted trajectory. The object trajectory is modeled obtained by projecting the face patterns into an KDA feature space is estimated. The approach for speaker's face identification by using synthesise the identity surface of a subject face from a small sample of patterns which sparsely each the view sphere. An KDA algorithm use to the Lip-reading image is discrimination, after that work consisted of in the low dimensional for the fundamental lip features vector is reduced by using the 2D-DCT.The mouth of the set area dimensionality is ordered by a normally reduction base on the PCA to obtain the Eigen lips approach, their proposed approach by[33]. The subjective performance results of the cost function under the automatic lips reading modeled , which wasn’t illustrate the superior performance of the
method.
MOVING FROM WATERFALL TO AGILE PROCESS IN SOFTWARE ENGINEERING CAPSTONE PROJE...cscpconf
Universities offer software engineering capstone course to simulate a real world-working environment in which students can work in a team for a fixed period to deliver a quality product. The objective of the paper is to report on our experience in moving from Waterfall process to Agile process in conducting the software engineering capstone project. We present the capstone course designs for both Waterfall driven and Agile driven methodologies that highlight the structure, deliverables and assessment plans.To evaluate the improvement, we conducted a survey for two different sections taught by two different instructors to evaluate students’ experience in moving from traditional Waterfall model to Agile like process. Twentyeight students filled the survey. The survey consisted of eight multiple-choice questions and an open-ended question to collect feedback from students. The survey results show that students were able to attain hands one experience, which simulate a real world-working environment. The results also show that the Agile approach helped students to have overall better design and avoid mistakes they have made in the initial design completed in of the first phase of the capstone project. In addition, they were able to decide on their team capabilities, training needs and thus learn the required technologies earlier which is reflected on the final product quality
PROMOTING STUDENT ENGAGEMENT USING SOCIAL MEDIA TECHNOLOGIEScscpconf
This document discusses using social media technologies to promote student engagement in a software project management course. It describes the course and objectives of enhancing communication. It discusses using Facebook for 4 years, then switching to WhatsApp based on student feedback, and finally introducing Slack to enable personalized team communication. Surveys found students engaged and satisfied with all three tools, though less familiar with Slack. The conclusion is that social media promotes engagement but familiarity with the tool also impacts satisfaction.
A SURVEY ON QUESTION ANSWERING SYSTEMS: THE ADVANCES OF FUZZY LOGICcscpconf
In real world computing environment with using a computer to answer questions has been a human dream since the beginning of the digital era, Question-answering systems are referred to as intelligent systems, that can be used to provide responses for the questions being asked by the user based on certain facts or rules stored in the knowledge base it can generate answers of questions asked in natural , and the first main idea of fuzzy logic was to working on the problem of computer understanding of natural language, so this survey paper provides an overview on what Question-Answering is and its system architecture and the possible relationship and
different with fuzzy logic, as well as the previous related research with respect to approaches that were followed. At the end, the survey provides an analytical discussion of the proposed QA models, along or combined with fuzzy logic and their main contributions and limitations.
DYNAMIC PHONE WARPING – A METHOD TO MEASURE THE DISTANCE BETWEEN PRONUNCIATIONS cscpconf
Human beings generate different speech waveforms while speaking the same word at different times. Also, different human beings have different accents and generate significantly varying speech waveforms for the same word. There is a need to measure the distances between various words which facilitate preparation of pronunciation dictionaries. A new algorithm called Dynamic Phone Warping (DPW) is presented in this paper. It uses dynamic programming technique for global alignment and shortest distance measurements. The DPW algorithm can be used to enhance the pronunciation dictionaries of the well-known languages like English or to build pronunciation dictionaries to the less known sparse languages. The precision measurement experiments show 88.9% accuracy.
INTELLIGENT ELECTRONIC ASSESSMENT FOR SUBJECTIVE EXAMS cscpconf
In education, the use of electronic (E) examination systems is not a novel idea, as Eexamination systems have been used to conduct objective assessments for the last few years. This research deals with randomly designed E-examinations and proposes an E-assessment system that can be used for subjective questions. This system assesses answers to subjective questions by finding a matching ratio for the keywords in instructor and student answers. The matching ratio is achieved based on semantic and document similarity. The assessment system is composed of four modules: preprocessing, keyword expansion, matching, and grading. A survey and case study were used in the research design to validate the proposed system. The examination assessment system will help instructors to save time, costs, and resources, while increasing efficiency and improving the productivity of exam setting and assessments.
TWO DISCRETE BINARY VERSIONS OF AFRICAN BUFFALO OPTIMIZATION METAHEURISTICcscpconf
African Buffalo Optimization (ABO) is one of the most recent swarms intelligence based metaheuristics. ABO algorithm is inspired by the buffalo’s behavior and lifestyle. Unfortunately, the standard ABO algorithm is proposed only for continuous optimization problems. In this paper, the authors propose two discrete binary ABO algorithms to deal with binary optimization problems. In the first version (called SBABO) they use the sigmoid function and probability model to generate binary solutions. In the second version (called LBABO) they use some logical operator to operate the binary solutions. Computational results on two knapsack problems (KP and MKP) instances show the effectiveness of the proposed algorithm and their ability to achieve good and promising solutions.
DETECTION OF ALGORITHMICALLY GENERATED MALICIOUS DOMAINcscpconf
In recent years, many malware writers have relied on Dynamic Domain Name Services (DDNS) to maintain their Command and Control (C&C) network infrastructure to ensure a persistence presence on a compromised host. Amongst the various DDNS techniques, Domain Generation Algorithm (DGA) is often perceived as the most difficult to detect using traditional methods. This paper presents an approach for detecting DGA using frequency analysis of the character distribution and the weighted scores of the domain names. The approach’s feasibility is demonstrated using a range of legitimate domains and a number of malicious algorithmicallygenerated domain names. Findings from this study show that domain names made up of English characters “a-z” achieving a weighted score of < 45 are often associated with DGA. When a weighted score of < 45 is applied to the Alexa one million list of domain names, only 15% of the domain names were treated as non-human generated.
GLOBAL MUSIC ASSET ASSURANCE DIGITAL CURRENCY: A DRM SOLUTION FOR STREAMING C...cscpconf
The document proposes a blockchain-based digital currency and streaming platform called GoMAA to address issues of piracy in the online music streaming industry. Key points:
- GoMAA would use a digital token on the iMediaStreams blockchain to enable secure dissemination and tracking of streamed content. Content owners could control access and track consumption of released content.
- Original media files would be converted to a Secure Portable Streaming (SPS) format, embedding watermarks and smart contract data to indicate ownership and enable validation on the blockchain.
- A browser plugin would provide wallets for fans to collect GoMAA tokens as rewards for consuming content, incentivizing participation and addressing royalty discrepancies by recording
IMPORTANCE OF VERB SUFFIX MAPPING IN DISCOURSE TRANSLATION SYSTEMcscpconf
This document discusses the importance of verb suffix mapping in discourse translation from English to Telugu. It explains that after anaphora resolution, the verbs must be changed to agree with the gender, number, and person features of the subject or anaphoric pronoun. Verbs in Telugu inflect based on these features, while verbs in English only inflect based on number and person. Several examples are provided that demonstrate how the Telugu verb changes based on whether the subject or pronoun is masculine, feminine, neuter, singular or plural. Proper verb suffix mapping is essential for generating natural and coherent translations while preserving the context and meaning of the original discourse.
EXACT SOLUTIONS OF A FAMILY OF HIGHER-DIMENSIONAL SPACE-TIME FRACTIONAL KDV-T...cscpconf
In this paper, based on the definition of conformable fractional derivative, the functional
variable method (FVM) is proposed to seek the exact traveling wave solutions of two higherdimensional
space-time fractional KdV-type equations in mathematical physics, namely the
(3+1)-dimensional space–time fractional Zakharov-Kuznetsov (ZK) equation and the (2+1)-
dimensional space–time fractional Generalized Zakharov-Kuznetsov-Benjamin-Bona-Mahony
(GZK-BBM) equation. Some new solutions are procured and depicted. These solutions, which
contain kink-shaped, singular kink, bell-shaped soliton, singular soliton and periodic wave
solutions, have many potential applications in mathematical physics and engineering. The
simplicity and reliability of the proposed method is verified.
AUTOMATED PENETRATION TESTING: AN OVERVIEWcscpconf
The document discusses automated penetration testing and provides an overview. It compares manual and automated penetration testing, noting that automated testing allows for faster, more standardized and repeatable tests but has limitations in developing new exploits. It also reviews some current automated penetration testing methodologies and tools, including those using HTTP/TCP/IP attacks, linking common scanning tools, a Python-based tool targeting databases, and one using POMDPs for multi-step penetration test planning under uncertainty. The document concludes that automated testing is more efficient than manual for known vulnerabilities but cannot replace manual testing for discovering new exploits.
CLASSIFICATION OF ALZHEIMER USING fMRI DATA AND BRAIN NETWORKcscpconf
Since the mid of 1990s, functional connectivity study using fMRI (fcMRI) has drawn increasing
attention of neuroscientists and computer scientists, since it opens a new window to explore
functional network of human brain with relatively high resolution. BOLD technique provides
almost accurate state of brain. Past researches prove that neuro diseases damage the brain
network interaction, protein- protein interaction and gene-gene interaction. A number of
neurological research paper also analyse the relationship among damaged part. By
computational method especially machine learning technique we can show such classifications.
In this paper we used OASIS fMRI dataset affected with Alzheimer’s disease and normal
patient’s dataset. After proper processing the fMRI data we use the processed data to form
classifier models using SVM (Support Vector Machine), KNN (K- nearest neighbour) & Naïve
Bayes. We also compare the accuracy of our proposed method with existing methods. In future,
we will other combinations of methods for better accuracy.
VALIDATION METHOD OF FUZZY ASSOCIATION RULES BASED ON FUZZY FORMAL CONCEPT AN...cscpconf
The document proposes a new validation method for fuzzy association rules based on three steps: (1) applying the EFAR-PN algorithm to extract a generic base of non-redundant fuzzy association rules using fuzzy formal concept analysis, (2) categorizing the extracted rules into groups, and (3) evaluating the relevance of the rules using structural equation modeling, specifically partial least squares. The method aims to address issues with existing fuzzy association rule extraction algorithms such as large numbers of extracted rules, redundancy, and difficulties with manual validation.
PROBABILITY BASED CLUSTER EXPANSION OVERSAMPLING TECHNIQUE FOR IMBALANCED DATAcscpconf
In many applications of data mining, class imbalance is noticed when examples in one class are
overrepresented. Traditional classifiers result in poor accuracy of the minority class due to the
class imbalance. Further, the presence of within class imbalance where classes are composed of
multiple sub-concepts with different number of examples also affect the performance of
classifier. In this paper, we propose an oversampling technique that handles between class and
within class imbalance simultaneously and also takes into consideration the generalization
ability in data space. The proposed method is based on two steps- performing Model Based
Clustering with respect to classes to identify the sub-concepts; and then computing the
separating hyperplane based on equal posterior probability between the classes. The proposed
method is tested on 10 publicly available data sets and the result shows that the proposed
method is statistically superior to other existing oversampling methods.
CHARACTER AND IMAGE RECOGNITION FOR DATA CATALOGING IN ECOLOGICAL RESEARCHcscpconf
Data collection is an essential, but manpower intensive procedure in ecological research. An
algorithm was developed by the author which incorporated two important computer vision
techniques to automate data cataloging for butterfly measurements. Optical Character
Recognition is used for character recognition and Contour Detection is used for imageprocessing.
Proper pre-processing is first done on the images to improve accuracy. Although
there are limitations to Tesseract’s detection of certain fonts, overall, it can successfully identify
words of basic fonts. Contour detection is an advanced technique that can be utilized to
measure an image. Shapes and mathematical calculations are crucial in determining the precise
location of the points on which to draw the body and forewing lines of the butterfly. Overall,
92% accuracy were achieved by the program for the set of butterflies measured.
SOCIAL MEDIA ANALYTICS FOR SENTIMENT ANALYSIS AND EVENT DETECTION IN SMART CI...cscpconf
Smart cities utilize Internet of Things (IoT) devices and sensors to enhance the quality of the city
services including energy, transportation, health, and much more. They generate massive
volumes of structured and unstructured data on a daily basis. Also, social networks, such as
Twitter, Facebook, and Google+, are becoming a new source of real-time information in smart
cities. Social network users are acting as social sensors. These datasets so large and complex
are difficult to manage with conventional data management tools and methods. To become
valuable, this massive amount of data, known as 'big data,' needs to be processed and
comprehended to hold the promise of supporting a broad range of urban and smart cities
functions, including among others transportation, water, and energy consumption, pollution
surveillance, and smart city governance. In this work, we investigate how social media analytics
help to analyze smart city data collected from various social media sources, such as Twitter and
Facebook, to detect various events taking place in a smart city and identify the importance of
events and concerns of citizens regarding some events. A case scenario analyses the opinions of
users concerning the traffic in three largest cities in the UAE
SOCIAL NETWORK HATE SPEECH DETECTION FOR AMHARIC LANGUAGEcscpconf
The anonymity of social networks makes it attractive for hate speech to mask their criminal
activities online posing a challenge to the world and in particular Ethiopia. With this everincreasing
volume of social media data, hate speech identification becomes a challenge in
aggravating conflict between citizens of nations. The high rate of production, has become
difficult to collect, store and analyze such big data using traditional detection methods. This
paper proposed the application of apache spark in hate speech detection to reduce the
challenges. Authors developed an apache spark based model to classify Amharic Facebook
posts and comments into hate and not hate. Authors employed Random forest and Naïve Bayes
for learning and Word2Vec and TF-IDF for feature selection. Tested by 10-fold crossvalidation,
the model based on word2vec embedding performed best with 79.83%accuracy. The
proposed method achieve a promising result with unique feature of spark for big data.
GENERAL REGRESSION NEURAL NETWORK BASED POS TAGGING FOR NEPALI TEXTcscpconf
This article presents Part of Speech tagging for Nepali text using General Regression Neural
Network (GRNN). The corpus is divided into two parts viz. training and testing. The network is
trained and validated on both training and testing data. It is observed that 96.13% words are
correctly being tagged on training set whereas 74.38% words are tagged correctly on testing
data set using GRNN. The result is compared with the traditional Viterbi algorithm based on
Hidden Markov Model. Viterbi algorithm yields 97.2% and 40% classification accuracies on
training and testing data sets respectively. GRNN based POS Tagger is more consistent than the
traditional Viterbi decoding technique.
How to Restrict Price Modification to Managers in Odoo 17 POSCeline George
This slide will represent the price control functionality in Odoo 17 PoS module. This feature provides the opportunity to restrict price adjustments. We can limit pricing changes to managers exclusively with it.
What is the Use of API.onchange in Odoo 17Celine George
The @api.onchange decorator in Odoo is indeed used to trigger a method when a field's value changes. It's commonly used for validating data or triggering actions based on the change of a specific field. When the field value changes, the function decorated with @api.onchange will be called automatically.
Bipolar Junction Transistors and operation .pptxnitugatkal
A transistor is a type of semiconductor device that can be used to conduct and insulate electric current or voltage. A transistor basically acts as a switch and an amplifier.
How to install python packages from PycharmCeline George
In this slide, let's discuss how to install Python packages from PyCharm. In case we do any customization in our Odoo environment, sometimes it will be necessary to install some additional Python packages. Let’s check how we can do this from PyCharm.
How to Integrate Facebook in Odoo 17 - Odoo 17 SlidesCeline George
Integrating Facebook with other platforms, such as business software like Odoo, serves several purposes and can offer numerous benefits depending on the specific goals of your business.
Vortrag auf der Sub-Konferenz "Planning, democracy and postcapitalism" als Teil der Jahrestagung der französischen Assoziation für politische Ökonomie (Association française d’économie politique) 2024 in Montpellier/Frankreich.
How to Use Serial Numbers to Track Products in Odoo 17 InventoryCeline George
Mainly lots or serial numbers are used for tracking the products. Lots are actually the codes that applied for collection of products. But serial numbers are distinct numbers allocated for a particular product. Lots and serial numbers in the products will help to manage the inventory, to trace the products that reached their expiry date. This slide will show how to use lots and serial numbers to track products in odoo 17 inventory.
A history of Innisfree in Milanville, PennsylvaniaThomasRue2
A history of Innisfree in Milanville, Damascus Township, Wayne County, Pennsylvania. By TOM RUE, July 23, 2023. Innisfree began as "an experiment in democracy," modeled after A.S. Neill's "Summerhill" school in England, "the first libertarian school".
Introduction to Literary Criticism 10 (1).pptxjessintv
Introduction to Literary Criticism prepared by Mrs.V.Jesinthal Mary,Asst.Professor,Dept of English and other foreign Languages (EFL), SRMIST Science and Humanities, Ramapuram,
Chennai-600089
Stéphan Vincent-Lancrin, Deputy Head of IMEP division and Senior Analyst - P...EduSkills OECD
Stéphan Vincent-Lancrin, Deputy Head of IMEP division and Senior Analyst - Presentation at the OECD Webinar Battling AI bias in the classroom on 25 July 2024
2. 68 Computer Science & Information Technology (CS & IT)
purpose modeling language in the field of object-oriented software engineering. The standard is
managed, and was created, by the Object Management Group. It was first added to the list of
OMG adopted technologies in 1997, and has since become the industry standard for modeling
software-intensive systems. In software and systems engineering, a use case is a list of steps,
typically defining interactions between a role (known in UML as an "actor") and a system, to
achieve a goal. The actor can be a human or an external system. Use cases represent the things of
value that the system performs for its actors. Use cases are not functions or features, and they
cannot be decomposed. Use cases have a name and a brief description. They also have detailed
descriptions that are essentially, stories about how the actors use the system to do something they
consider important, and what the system does to satisfy these needs. In computer science,
abstraction is the process by which data and programs are defined with a representation similar in
form to its meaning (semantics), while hiding away the implementation details. Abstraction tries
to reduce and factor out details so that the programmer can focus on a few concepts at a time. A
system can have several abstraction layers whereby different meanings and amounts of detail are
exposed to the programmer. For example, low-level abstraction layers expose details of the
computer hardware where the program is run, while high-level layers deal with the business logic
of the program. We will investigate abstraction of data in use cases.
2. USE CASE MODELING
Use case modeling is to capture the system (to be) requirements making use of UML diagrams
like- Use case diagram, class diagram, activity diagram, sequence diagram and state-chart
diagram. It may further include other diagram as and when required. A use-case model is a model
of how different types of users interact with the system to solve a problem. As such, it describes
the goals of the users, the interactions between the users and the system, and the required
behavior of the system in satisfying these goals. A use-case model consists of a number of model
elements. The most important model elements are: use cases, actors and the relationships
between them. A use-case diagram is used to graphically depict a subset of the model to simplify
communications. There will typically be several use-case diagrams associated with a given
model, each showing a subset of the model elements relevant for a particular purpose. The same
model element may be shown on several use-case diagrams, but each instance must be consistent.
If tools are used to maintain the use-case model, this consistency constraint is automated so that
any changes to the model element (changing the name for example) will be automatically
reflected on every use-case diagram that shows that element. The use-case model may contain
packages that are used to structure the model to simplify analysis, communications, navigation,
development, maintenance and planning. Much of the use-case model is in fact textual, with the
text captured in the use-case specifications that are associated with each use-case model element.
These specifications describe the flow of events of the use case. The use-case model serves as a
unifying thread throughout system development. It is used as the primary specification of the
functional requirements for the system, as the basis for analysis and design, as an input to
iteration planning, as the basis of defining test cases and as the basis for user documentation.
3. ABSTRACTION AND DATA ABSTRACTION
Abstraction captures only those details about an object that are relevant to the current perspective.
The concept originated by analogy with abstraction in mathematics. The mathematical technique
of abstraction begins with mathematical definitions, making it a more technical approach than the
general concept of abstraction in philosophy. For example, in both computing and in
3. Computer Science & Information Technology (CS & IT) 69
mathematics, numbers are concepts in the programming languages, as founded in mathematics.
Implementation details depend on the hardware and software, but this is not a restriction because
the computing concept of number is still based on the mathematical concept. Data abstraction
refers to, providing only essential information to the outside word and hiding their background
details i.e. representing the needed information in program without presenting the details. Data
abstraction is a programming (and design) technique that relies on the separation of interface and
implementation. Let's take one real life example of a TV which you can turn on and off, change
the channel, adjust the volume, and add external components such as speakers, VCRs, and DVD
players BUT you do not know it's internal detail that is, you do not know how it receives signals
over the air or through a cable, how it translates them, and finally displays them on the screen.
Thus we can say, a television clearly separates its internal implementation from its external
interface and you can play with its interfaces like the power button, channel changer, and volume
control without having zero knowledge of its internals. Now if we talk in terms of C++
Programming, C++ classes provides great level of data abstraction. They provide sufficient public
methods to the outside world to play with the functionality of the object and to manipulate object
data ie. state without actually knowing how class has been implemented internally. Abstraction is
the process of recognizing and focusing on important characteristics of a situation or object and
leaving/filtering out the un-wanted characteristics of that situation or object. So, you see that
Abstraction is the basis for software development. It’s through abstraction we define the essential
aspects of a system. The process of identifying the abstractions for a given system is called as
Modeling (or object modeling). So, we see that abstraction is the basis for object oriented
programming. Abstraction serves as the foundation for determining the classes for a particular
system (which is called object model). But be advised, there is no acid test to decide if the
abstraction for a given system is right or wrong. A "person" abstraction for a hospital information
system would be different from a person abstraction for a library information system and even
with hospital information system, person abstraction may be different for different projects. Once
you have abstracted an object, it can be re-used. It can be modified to suit other situations. As a
child you learnt Tri-cycle. You used the experience of learning tri-cycle (handle bar control,
pedaling) to learn bicycling. What actually you do to learn bicycling is that you only learn to
balance the bicycle while you use the experience of tricycle to use handlebar and pedaling. The
same case applies to abstraction as well. Though abstraction seems to be a simple concept, it’s a
challenging task. The reasons are
1. There are un-limited numbers of possibilities to define an abstraction for a situation.
2. As mentioned earlier, there is no acid test to determine if the abstraction is right or wrong.
You end up discussing, arguing with your counterpart that yours is best and his is worst…. He
does the same thing…
However, these problems are always addressed as you gain experience (which you can gain by
reading more books/articles and doing real time projects) in defining the abstraction. Abstraction
by itself is a huge and an interesting concept. But, we feel that most of the people, who define
4. EXAMPLE – HOW TO ABSTRACT DATA
It is an important step to abstract data. Data is abstracted from the steps involved in describing the
behavior. Use case is made up of such steps. In each step of event we abstract data. An example is
shown as below.
4. 70 Computer Science & Information Technology (CS & IT)
Table 1. Data Abstraction Example
Activity- “ Open the door”
Behavioral Steps
Walk till the door
Catch the knob of the door
Swing the knob clockwise
Push the door
Data Abstraction
Distance - meters
Force value - Kilograms
Angle of swing in degrees
Direction of swing
Door Size – meter x meter
Force of Push - kilograms
The above example gives the details of the data abstraction for a simple task- ‘open the door’ in
real life. The steps involved can be seen as the actions performed to fulfill a use case named-
Open the Door. The right column depicts the data to be abstracted. First of all to reach the door
one has to walk some distance- distance walked is the data associated with this step. Further when
the person reaches the door he catches the knob of the door. In order to catch the knob one needs
some force to be applied on the door.
5. CASE STUDY INVESTIGATIONS – E-RETAIL SYSTEM
Unified process and UML have special representations for use cases and actors. A simple ellipse
represents use cases; simple stick figures, actors. A use case diagram expresses the system's use
cases in relation to the actors that invoke them. We prefer to construct these diagrams with an
adornment that draws a boundary around the system, placing the use cases within the boundary
and the actors outside Figure 1 as shown below. This notation is convenient when multiple
systems are being jointly developed, and it can be clearly seen which use cases are part of which
system. The complete collection of use cases, actors, and diagrams forms a use case model,
which, like individual use cases, is just one part of the system's requirements specification.
Fig. 1. Use Case Model for E-Retail System
5. Computer Science & Information Technology (CS & IT) 71
Relationships between actors and use cases indicate that the actor can invoke a particular use
case. Figure 8-4 shows that the actor can browse the catalog or check on the order status. This
diagram also identifies two other actors: the Merchant Account System and the Shipping
Department. These actors are in fact not individuals but rather external systems, or more
accurately the APIs of those external systems. When the Process Payment use case is invoked, it
initiates the dialogue between the Merchant Account System and this system; similarly, the Ship
Order use case contacts the Shipping Department's system when invoked. Relationships between
use cases are also documented in the model and appear in a diagram as a stereotyped dependency
relationship, or arrow-headed dashed line. The two major types of relationships between use
cases are «includes» and «extends». Both indicate a dependency on one use case by the other;
however, the subtle difference between the two has, in my experience, caused a significant degree
of confusion. In Figure 1, the use case Checkout extends the use case Browse Catalog. This
means that the actor invoking the use case might decide to extend the dialogue with the system to
include the activities described in the Checkout use case. The key word here is "might." Every
invocation of the Browse Catalog use case does not necessarily include checking out. The
relationships between the Checkout use case and the Process Payment and Ship Order use cases,
however, are expected with every invocation of the Checkout use case. The «includes»
relationship indicates that each invocation of the Checkout use case will invoke the included use
cases at least once. This type of a relationship can be thought of as calling a subroutine. The use
case model shows the structural relationships between use cases but does not show dynamic
relationships, or workflows. Dynamic behaviors are expressed with interaction diagrams:
sequence, collaboration, and activity. It is important to keep that in mind when drawing use case
diagrams. It's easy to start constructing use case diagrams as if they were workflow diagrams,
since use case names often reflect major activities of the business workflow. Most associations
between use cases in a diagram simply imply that one invokes the other, nothing more. There's
more to the use case model than this high-level diagram. Some analysts recently have begun to
create a single activity diagram for each use case in the system. This activity diagram helps me
sort out all the alternative flows in a use case and ensure that we haven't forgotten how any of
them rejoins the basic flow. In the past, we drafted a few use cases in which later iterations added
alternative flows that seemed reasonable and addressed the issue at the time, but when it came to
implementing them, it wasn't clear in what state those alternative flows would leave the system
and at what point the normal flow of the use case scenario should resume. Properly created
activity diagrams for a use case clearly identify all alternative paths as branches and even allow
us to see the effects of repetition, or loops, in the flow that would otherwise be mentioned only in
the text of the use case specification. Figure 2, the activities for the Browse Catalog use case,
shows a typical activity diagram for a use case that has some repetition. It is clear from this
diagram that there is one main loop structure, labeled the Shop controller. Many of the branches
are guarded with conditions—text between the brackets—and indicate the availability of an
option that the actor can invoke. As a notational convention, we can add notes to the activity
diagram at those points where the use case is extended or included. If the modeling tool you use
supports the inclusion of hyperlinks to other diagrams, it is highly recommended, hyperlinking
these notes to the relevant activity diagram to make it easier for the reader to follow the flow
through all the related use cases. The activity diagram of a use case clarifies the nature of the
«includes» or «extends» relationships. In the case of an «extended» relationship, it should be
possible for the actor to get from the start activity to an end activity without invoking the
extended use case. Figure 2 demonstrates that it is possible for the actor to follow a path from
start to finish without hitting the Request Checkout activity and thus invoking the Checkout use
case.
6. 72 Computer Science & Information Technology (CS & IT)
6. INTRODUCING FORMALISM
We have suggested and investigated that Object Constraint Language (OCL) is very helpful to
gain accuracy and perfection. The Object Constraint Language is a declarative language for
describing rules that apply to Unified Modeling Language models developed at IBM and now
part of the UML standard. Initially, OCL was only a formal specification language extension to
UML. OCL may now be used with any Meta-Object Facility (MOF) Object Management Group
(OMG) meta-model, including UML. As an example, we have modeled a computer system for a
fictional company called Royal and Loyal (R&L). R&L handles loyalty programs for companies
that offer their customers various kinds of bonuses. Often, the extras take
Fig. 2. The figure shows the activity diagram for Browse Catalog Use Case
7. Computer Science & Information Technology (CS & IT) 73
the form of bonus points or air miles, but other bonuses are possible as well: reduced rates, a
larger rental car for the same price as a standard rental car, extra or better service on an airline,
and so on. Anything a company is willing to offer can be a service rendered in a loyalty program.
The central class in the model is LoyaltyProgram. A system that administers a single loyalty
program will contain only one instance of this class. In the case of R&L, many instances of this
class will be present in the system. A company that offers its customers membership in a loyalty
program is called a ProgramPartner. More than one company can enter the same program. In that
case, customers who enter the loyalty program can profit from services rendered by any of the
participating companies. Every customer of a program partner can enter the loyalty program by
filling in a form and obtaining a membership card. The objects of class Customer represent the
persons who have entered the program. The membership card, represented by the class
CustomerCard, is issued to one person. Card use is not checked, so a single card could be used for
an entire family or business. Most loyalty programs allow customers to save bonus points. Each
individual program partner decides when and how many bonus points are allotted for a certain
purchase. Saved bonus points can be used to "buy'' specific services from one of the program
partners. To account for the bonus points that are saved by a customer, every membership can be
associated with a LoyaltyAccount.
Various transactions on this account are possible. For example, the loyalty program "Silver and
Gold" has four program partners: a supermarket, a line of gas stations, a car rental service, and an
airline.
• At the supermarket, the customer can use bonus points to purchase items. The customer
earns five bonus points for any regular purchase over the amount of $25.
• The gas stations offer a discount of 5 percent on every purchase.
• The car rental service offers 20 bonus points for every $100 spent.
• Customers can save bonus points for free flights with the airline company. For every
flight that is paid for normally, the airline offers one bonus point for each 15 miles of
flight.
In this situation, there are two types of transactions. First, there are transactions in which the
customer obtains bonus points. In the model, these transactions are represented by a subclass of
Transaction called Earning. Second, there are transactions in which the customer spends bonus
points. In the model, they are represented by instances of the Burning subclass of Transaction.
The gas stations offer simple discounts but do not offer or accept bonus points. Because the
turnover generated by the customers need to be recorded, this is entered as two simultaneous
transactions on the LoyaltyAccount, one Earning and one Burning for the same number of points.
Customers in the Silver and Gold program who make extensive use of the membership are
rewarded with a higher level of service: the gold card. In addition to the regular services,
customers who have a gold card are also offered the following additional services:
• Every two months, the supermarket offers an item that is completely free. The average
value of the item is $25.
• The gas stations offer a discount of 10 percent on every purchase.
• The car rental service offers a larger car for the same price.
• The airline offers its gold card customers a business class seat for the economy class
price.
Customers must meet at least one of the following conditions to get a gold card:
8. 74 Computer Science & Information Technology (CS & IT)
• Three sequential years of membership with an average annual turnover of $5,000
• One year of membership with a turnover of $15,000, where the turnover is the total
turnover with all program partners
To administer different levels of service, the class ServiceLevel is introduced in the model. A
service level is defined by the loyalty program and used for each membership.
R&L advertises the program and its conditions. It manages all customer data and transactions on
the loyalty accounts. For this purpose, the program partners must inform R&L of all transactions
on loyalty program membership cards. Each year, R&L sends new membership cards to all
customers. When appropriate, R&L upgrades a membership card to a gold card. In this case,
R&L sends the customer a new gold card along with information about the additional services
offered, and R&L invalidates the old membership card.
The customer can withdraw from the program by sending a withdrawal form to R&L. Any
remaining bonus points are canceled and the card is invalidated. R&L can invalidate a
membership when the customer has not used the membership card for a certain period. For the
Silver and Gold program, this period is one year. Initial values and derivation rules will be as
follows.
context LoyaltyAccount::points
init: 0
context CustomerCard::valid
init: true
context CustomerCard::printedName
derive: owner.title.concat(' ').concat(owner.name)
In this case, the refined query operation can be specified as follows:
context LoyaltyProgram::getServices(pp: ProgramPartner)
: Set(Service)
body: if partners->includes(pp)
then pp.deliveredServices
else Set
endif
7. SUMMARY
We see that there is great importance of data abstraction in early stages of life cycle. The process
involves identifying use cases and then after finding out actors and use cases, we describe the
events performed by the system and the actor. This is called the flow of events required to
complete a uses case basic flow or any other use case scenario. Inside the flow of events, there is
hidden data. Actually in these set of flow of events we expect behavior performed by the
interaction of actor and the system. Behavior is the key to find out or abstract data. Now in order
to find out data we carefully understand the flow of event step by step and abstract data.
Formalization contributes to the accurateness of the data abstraction. We have examined and
explored object constraint language to perform improved data abstraction during analysis &
9. Computer Science & Information Technology (CS & IT) 75
design in unified paradigm. In this paper we have presented our research regarding early stage
data abstraction and its formalization.
REFERENCES
[1] Beck, Kent: Extreme Programming Explained: Embrace Change. Addison-Wesley, Boston, 2000.
[2] Block, Robert: The Politics of Projects. Yourdon Press, New York, NY, 1983.
[3] BridgePoint Object Action Language Manual www.projtech.com/pdfs/bp/oal.pdf
[4] BridgePoint Object Action Language www.projtech.com/pdfs/bp/oal.pdf
[5] Cockburn, Alistair: Writing Effective Use Cases. Addison-Wesley, Boston, 2001.
[6] Communications of the ACM, Volume 44, Issue 10. (The entire issue is devoted to aspect-oriented
development.)
[7] Constantine, Larry, and Lucy Lockwood: Software for Use: A Practical Guide to the Models and
Methods of Usage-Centered Design. Addison-Wesley, Reading Mass., >1999.
[8] Fowler, Martin: "Use and Abuse Cases." In Distributed Computing, April 1998.
[9] Harel, D. "Statecharts: A visual formalism for complex systems." In Science of Computer
Programming 8, 3 (June 1987), 231–274.
[10] Jacobson, Ivar, et al.: Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-
Wesley, Reading, Mass., 1992.
[11] Kabira Technologies URL: www.kabira.com
[12] Lamport, Leslie, and P. M. Melliar-Smith. "Synchronizing clocks in the presence of faults," in Journal
of the ACM, 32(1):52–78, January 1985.
[13] Mellor,Stephen J., Steve Tockey, Rodolphe Arthaud, and Philippe Leblanc: Software-Platform-
Independent, Precise Action Specifications for UML. In Proceedings of «UML 98».
[14] Page-Jones, Meilir: Fundamentals of Object-Oriented Design in UML. Addison-Wesley, Boston,
2000.
[15] Palahniuk, Chuck: Fight Club. WW Norton and Company, 1996. "The first rule of Fight Club is you
do not talk about Fight Club. The second rule of Fight Club is you do not talk about Fight Club."
[16] Project Technology, Inc. URL: www.projtech.com
[17] Rumbaugh, James: The Unified Modeling Language Reference Manual. Addison-Wesley, Reading
MA, 1998
[18] Shlaer, Sally, and Stephen J. Mellor: Object Lifecycles: Modeling the World in States. Prentice Hall
PTR, Englewood Cliffs, N.J., 1992
[19] Shlaer, Sally, and Stephen J. Mellor: Object Lifecycles: Modeling the World in States. Prentice Hall
PTR , Englewood Cliffs, N.J., 1992.
[20] Shlaer, Sally, and Stephen J. Mellor: Object-Oriented Systems Analysis: Modeling the World in Data.
Prentice-