1) UCD-Generator is an application that uses natural language processing to automatically generate use case diagrams from plain English requirements.
2) It analyzes the text using LESSA, which performs tokenization, part-of-speech tagging, and meaning understanding to extract actors, actions, and objects.
3) It then generates use case diagrams in two phases - first extracting information, then drawing the diagrams based on that information. Experiments showed it could accurately generate diagrams for 85% of scenarios.
Imran Sarwar Bajwa, M. Abbas Choudhary [2006], "Natural Language Processing based Automated System for UML Diagrams Generation", in Saudi 18th National Conference on Computer Application, 2006, (18th NCCA) Riyadh, Kingdom of Saudi Arabia pp:171-176
Automated Java Code Generation (ICDIM 2006)IT Industry
Rule based Production Systems for Automatic Code Generation in Java
This document describes a system that can automatically generate UML diagrams and code from natural language requirements. It analyzes text written in English to extract objects, classes, attributes and methods. It then generates UML class, activity, sequence and use case diagrams based on the analysis. Finally, it produces code in languages like Java, C# and VB.NET corresponding to the diagrams. The system aims to save time and costs by automating modeling and a significant portion of coding based on input requirements. It provides a more efficient alternative to traditional manual modeling and coding approaches.
Imran Sarwar Bajwa, M. Abbas Choudhary [2006], "Automatic Web Layout Generation using Natural Language Processing Techniques", in 2nd International Conference From Scientific Computing to Computational Engineering, (IC-SCCE 2006) Athens, Greece, pp:334-340
Domain Specific Terminology Extraction (ICICT 2006)IT Industry
Imran Sarwar Bajwa, M. Imran Siddique, M. Abbas Choudhary, [2006], "Automatic Domain Specific Terminology Extraction using a Decision Support System", in IEEE 4th International Conference on Information and Communication Technology (ICICT 2006), Cairo, Egypt. pp:651-659
NL based Object Oriented modeling - EJSR 35(1)IT Industry
Imran Sarwar Bajwa, Shahzad Mumtaz, Ali Samad [2009], "Object Oriented Software Modeling using NLP Based Knowledge Extraction", European Journal of Scientific Research, Aug 2009, Vol. 35 No. 01, pp:22-33
MASRML - A DOMAIN-SPECIFIC MODELING LANGUAGE FOR MULTI-AGENT SYSTEMS REQUIREM...ijseajournal
MASRML – Multi-Agent Systems Requirements Modeling Language – is a UML-based Domain-Specific Modeling Language conceived for the requirements modeling in multi-agent system projects. Along this work the extended metamodel developed to support the language is described and the applicability of this DSML in the requirements identification of a multi-agent system is demonstrated using the new mechanisms produced to model specific functional requirements for this kind of system. This work also includes how the DSML was validated and the impressions collected during the validations.
Imran Sarwar Bajwa, [2010], "Markov Logics Based Automated Business Requirements Analysis", in International Journal of Computer and Electrical Engineering (IJCEE) 2(3) pp:481-485, June 2010
Introduction to the User Interface domain for business applications, a pattern based approach to model the UI and code generation techniques to make it possible.
Session for Code Generation 2011
Imran Sarwar Bajwa, M. Abbas Choudhary [2006], "Natural Language Processing based Automated System for UML Diagrams Generation", in Saudi 18th National Conference on Computer Application, 2006, (18th NCCA) Riyadh, Kingdom of Saudi Arabia pp:171-176
Automated Java Code Generation (ICDIM 2006)IT Industry
Rule based Production Systems for Automatic Code Generation in Java
This document describes a system that can automatically generate UML diagrams and code from natural language requirements. It analyzes text written in English to extract objects, classes, attributes and methods. It then generates UML class, activity, sequence and use case diagrams based on the analysis. Finally, it produces code in languages like Java, C# and VB.NET corresponding to the diagrams. The system aims to save time and costs by automating modeling and a significant portion of coding based on input requirements. It provides a more efficient alternative to traditional manual modeling and coding approaches.
Imran Sarwar Bajwa, M. Abbas Choudhary [2006], "Automatic Web Layout Generation using Natural Language Processing Techniques", in 2nd International Conference From Scientific Computing to Computational Engineering, (IC-SCCE 2006) Athens, Greece, pp:334-340
Domain Specific Terminology Extraction (ICICT 2006)IT Industry
Imran Sarwar Bajwa, M. Imran Siddique, M. Abbas Choudhary, [2006], "Automatic Domain Specific Terminology Extraction using a Decision Support System", in IEEE 4th International Conference on Information and Communication Technology (ICICT 2006), Cairo, Egypt. pp:651-659
NL based Object Oriented modeling - EJSR 35(1)IT Industry
Imran Sarwar Bajwa, Shahzad Mumtaz, Ali Samad [2009], "Object Oriented Software Modeling using NLP Based Knowledge Extraction", European Journal of Scientific Research, Aug 2009, Vol. 35 No. 01, pp:22-33
MASRML - A DOMAIN-SPECIFIC MODELING LANGUAGE FOR MULTI-AGENT SYSTEMS REQUIREM...ijseajournal
MASRML – Multi-Agent Systems Requirements Modeling Language – is a UML-based Domain-Specific Modeling Language conceived for the requirements modeling in multi-agent system projects. Along this work the extended metamodel developed to support the language is described and the applicability of this DSML in the requirements identification of a multi-agent system is demonstrated using the new mechanisms produced to model specific functional requirements for this kind of system. This work also includes how the DSML was validated and the impressions collected during the validations.
Imran Sarwar Bajwa, [2010], "Markov Logics Based Automated Business Requirements Analysis", in International Journal of Computer and Electrical Engineering (IJCEE) 2(3) pp:481-485, June 2010
Introduction to the User Interface domain for business applications, a pattern based approach to model the UI and code generation techniques to make it possible.
Session for Code Generation 2011
1) Arulmozhivarman Govindarajan is seeking a job utilizing his Master's degree in Computer Systems and experience as a software engineer and IT specialist.
2) He has worked in India, Sweden, and Germany on projects involving website development, software module development, security systems testing, and key management systems.
3) His skills include programming, web design, testing, databases, and he has certifications in computer applications and hardware.
This document discusses specifying use cases at different levels of abstraction. It proposes specifying use cases in the SilabReq domain specific language at various levels, from high-level interaction specifications to lower-level UI details. This allows use cases to promote better communication between stakeholders and more rigorous specification as needed for model-driven engineering. The levels include interaction, behavior, and UI specifications. An example order system is used to illustrate the different abstraction levels.
The document discusses the development and use of a recruitment chatbot. It proposes that a chatbot could automate many time-consuming recruitment tasks like collecting candidate information, screening, and scheduling interviews. This would help address the challenges of sifting through large numbers of resumes and finding qualified candidates more efficiently. The document outlines the design and implementation of a recruitment chatbot using techniques like neural networks, machine learning, and generative dialogue models. It suggests chatbots could handle initial recruitment stages and free up recruiters to focus on human aspects of the process.
The document discusses the differences between analysis modeling and design engineering/modeling. Analysis involves understanding a problem, while design focuses on creating a solution. Models can be used to better understand problems in analysis or solutions in design. The key aspects of design engineering are then outlined, including translating requirements into a software blueprint, iterating on the design, and ensuring quality through guidelines such as modularity, information hiding, and functional independence. Common design concepts like abstraction, architecture, patterns, and classes are also explained.
This document proposes optimizing service oriented architecture to support e-learning with adaptive and intelligent features. It discusses how adaptive learning refers to technologies that can dynamically recognize the role and profile of each learner and respond accordingly. It also discusses different adaptive learning approaches like macro, micro, and constructivist-collaborative approaches. Intelligent tutoring systems that utilize artificial intelligence techniques are also discussed. The proposal aims to make adaptive and intelligent e-learning features available as standard reusable services via an optimized service oriented architecture to enhance the overall system.
This summary provides an overview of the key concepts discussed in the document:
1. The document discusses various object-oriented analysis and design concepts including use case modeling, the Unified Modeling Language (UML), activity diagrams, associations, aggregation, and composition.
2. It provides descriptions and examples of these concepts, such as defining use cases, actors, and use case diagrams. Activity diagrams are described as showing workflows and processes.
3. The document also discusses UML notation for modeling associations, including binary and ternary associations, and modeling cardinality ratios between associated classes.
The document discusses object-oriented analysis and design concepts like refinement, extensibility, and design for reusability. It provides details on different types of extensibility like white-box, black-box, and gray-box extensibility. It also discusses object-oriented database management systems and compares relational databases with object-oriented databases.
This document provides lecture notes on data structures that cover key topics including:
- Classifying data structures as simple, compound, linear, and non-linear and providing examples.
- Defining abstract data types and algorithms, and explaining their structure and properties.
- Discussing approaches for designing algorithms and issues related to time and space complexity.
- Covering searching techniques like linear search and sorting techniques including bubble sort, selection sort, and quick sort.
- Describing linear data structures like stacks, queues, and linked lists and non-linear structures like trees and graphs.
Shakti Singh is seeking a position as a lecturer in education. He has over 10 years of experience teaching computer science courses at the undergraduate and postgraduate levels. He has expertise in technologies like C#, ASP.NET, SQL Server, and .NET Framework. He also has experience developing web applications as a freelance web developer.
IRJET - Chatbot for HR Department using AIML and LSAIRJET Journal
The document proposes a chatbot for an HR department that uses artificial intelligence techniques. It uses Artificial Intelligence Markup Language (AIML) and Latent Semantic Analysis (LSA) to understand natural language queries and provide responses. For common queries and greetings, it uses template-based responses stored in AIML. For more complex queries, it uses LSA for natural language processing techniques like stemming to analyze the query and provide an appropriate response. It discusses how the chatbot could simplify tasks for HR users by allowing them to get information through natural language queries rather than navigating different pages on HR software.
Cs 2352 object oriented analysis and designandrewsasi
This document provides an overview of an introductory course on object-oriented analysis and design (OOAD). It covers object-oriented systems development methodology, including object basics like classes, objects, attributes, methods, encapsulation, and inheritance. It also discusses the object-oriented systems development life cycle, including activities like object-oriented analysis, design, prototyping, and testing. The unified approach and unified modeling language are presented as standard methodologies for OOAD.
The document summarizes the phases of the software development life cycle (SDLC) and provides details about system requirement specification for an army management system project. It describes the typical phases in SDLC models such as waterfall, spiral, agile etc. It then covers the specific phases in more detail - preliminary analysis, system analysis, design, development, integration and testing, acceptance and deployment, maintenance. Lastly, it discusses system requirement specification, including UML notations, diagrams to be used and provides a brief overview of class diagrams.
Anup Kumar Saha is seeking a challenging career in software development. He has over 8 years of experience in teaching and software development using technologies like Java, Spring, Hibernate, Oracle, and more. His experience includes roles at Cognizant, HCL Technologies, Ericsson, TCS, and others working on projects in various domains for clients like Airtel, GM, and others. He is currently an Assistant Professor but seeking new opportunities.
IRJET - A Review on Chatbot Design and Implementation TechniquesIRJET Journal
This document reviews techniques for designing and implementing chatbots. It discusses past works on chatbot design using techniques like neural machine translation and reinforcement learning. The document proposes developing a state-of-the-art chatbot using tools like DialogFlow, TensorFlow, Android Studio and Firebase, along with machine learning and deep learning techniques. It reviews papers on chatbot design and discusses their strengths, limitations, and potential for further improvement.
Md. Mashiur Rahman is seeking a full-time position in IT with an expected salary of 30,000 Taka. He has a Bachelor's degree in Electronics and Telecommunications Engineering and over 3 years of experience as a Senior IT Executive and IT Officer. His experience includes managing networking equipment, providing IT support, software maintenance, and developing websites. He is proficient in technologies like PHP, MySQL, and has strong communication and problem-solving skills.
The document provides details of a proposed mobile application called "Time Table & Event Reminder App" that allows users to set reminders for events like lectures or meetings. It includes an entity relationship diagram and class diagram that model the database structure, as well as use case, sequence, and collaboration diagrams that describe the interactions between users and the app. The app would allow both students and teachers to view schedules and set reminders for lectures, and also include a general reminder feature for other events.
The document provides an overview of a software engineering course syllabus and objectives. The syllabus covers 6 units: software process and agile development, requirements analysis and specification, object oriented concepts, software design, testing and management, and learning resources. The course objectives are to understand software project phases, requirements engineering, object oriented concepts, enterprise integration, and testing/project management techniques. Students will learn to compare process models, formulate requirements engineering concepts, understand object oriented fundamentals, apply software design procedures, and evaluate testing techniques and project schedules.
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.
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 an approach for automatically generating software artifacts and models from natural language requirements documents during the analysis phase of software development.
It proposes a technique that first converts the natural language into a formal Semantic Business Vocabulary and Rules (SBVR) format. It then performs semantic and syntactic analysis on the SBVR to identify software artifacts like actors, use cases, classes, attributes, methods, and relationships. These artifacts are used to generate analysis models like use case diagrams and class diagrams. Finally, it produces XML Metadata Interchange (XMI) files to visualize the generated models in a UML modeling tool. The goal is to increase accuracy over existing tools by using the SBVR intermediate representation and generating multiple analysis models rather
1) Arulmozhivarman Govindarajan is seeking a job utilizing his Master's degree in Computer Systems and experience as a software engineer and IT specialist.
2) He has worked in India, Sweden, and Germany on projects involving website development, software module development, security systems testing, and key management systems.
3) His skills include programming, web design, testing, databases, and he has certifications in computer applications and hardware.
This document discusses specifying use cases at different levels of abstraction. It proposes specifying use cases in the SilabReq domain specific language at various levels, from high-level interaction specifications to lower-level UI details. This allows use cases to promote better communication between stakeholders and more rigorous specification as needed for model-driven engineering. The levels include interaction, behavior, and UI specifications. An example order system is used to illustrate the different abstraction levels.
The document discusses the development and use of a recruitment chatbot. It proposes that a chatbot could automate many time-consuming recruitment tasks like collecting candidate information, screening, and scheduling interviews. This would help address the challenges of sifting through large numbers of resumes and finding qualified candidates more efficiently. The document outlines the design and implementation of a recruitment chatbot using techniques like neural networks, machine learning, and generative dialogue models. It suggests chatbots could handle initial recruitment stages and free up recruiters to focus on human aspects of the process.
The document discusses the differences between analysis modeling and design engineering/modeling. Analysis involves understanding a problem, while design focuses on creating a solution. Models can be used to better understand problems in analysis or solutions in design. The key aspects of design engineering are then outlined, including translating requirements into a software blueprint, iterating on the design, and ensuring quality through guidelines such as modularity, information hiding, and functional independence. Common design concepts like abstraction, architecture, patterns, and classes are also explained.
This document proposes optimizing service oriented architecture to support e-learning with adaptive and intelligent features. It discusses how adaptive learning refers to technologies that can dynamically recognize the role and profile of each learner and respond accordingly. It also discusses different adaptive learning approaches like macro, micro, and constructivist-collaborative approaches. Intelligent tutoring systems that utilize artificial intelligence techniques are also discussed. The proposal aims to make adaptive and intelligent e-learning features available as standard reusable services via an optimized service oriented architecture to enhance the overall system.
This summary provides an overview of the key concepts discussed in the document:
1. The document discusses various object-oriented analysis and design concepts including use case modeling, the Unified Modeling Language (UML), activity diagrams, associations, aggregation, and composition.
2. It provides descriptions and examples of these concepts, such as defining use cases, actors, and use case diagrams. Activity diagrams are described as showing workflows and processes.
3. The document also discusses UML notation for modeling associations, including binary and ternary associations, and modeling cardinality ratios between associated classes.
The document discusses object-oriented analysis and design concepts like refinement, extensibility, and design for reusability. It provides details on different types of extensibility like white-box, black-box, and gray-box extensibility. It also discusses object-oriented database management systems and compares relational databases with object-oriented databases.
This document provides lecture notes on data structures that cover key topics including:
- Classifying data structures as simple, compound, linear, and non-linear and providing examples.
- Defining abstract data types and algorithms, and explaining their structure and properties.
- Discussing approaches for designing algorithms and issues related to time and space complexity.
- Covering searching techniques like linear search and sorting techniques including bubble sort, selection sort, and quick sort.
- Describing linear data structures like stacks, queues, and linked lists and non-linear structures like trees and graphs.
Shakti Singh is seeking a position as a lecturer in education. He has over 10 years of experience teaching computer science courses at the undergraduate and postgraduate levels. He has expertise in technologies like C#, ASP.NET, SQL Server, and .NET Framework. He also has experience developing web applications as a freelance web developer.
IRJET - Chatbot for HR Department using AIML and LSAIRJET Journal
The document proposes a chatbot for an HR department that uses artificial intelligence techniques. It uses Artificial Intelligence Markup Language (AIML) and Latent Semantic Analysis (LSA) to understand natural language queries and provide responses. For common queries and greetings, it uses template-based responses stored in AIML. For more complex queries, it uses LSA for natural language processing techniques like stemming to analyze the query and provide an appropriate response. It discusses how the chatbot could simplify tasks for HR users by allowing them to get information through natural language queries rather than navigating different pages on HR software.
Cs 2352 object oriented analysis and designandrewsasi
This document provides an overview of an introductory course on object-oriented analysis and design (OOAD). It covers object-oriented systems development methodology, including object basics like classes, objects, attributes, methods, encapsulation, and inheritance. It also discusses the object-oriented systems development life cycle, including activities like object-oriented analysis, design, prototyping, and testing. The unified approach and unified modeling language are presented as standard methodologies for OOAD.
The document summarizes the phases of the software development life cycle (SDLC) and provides details about system requirement specification for an army management system project. It describes the typical phases in SDLC models such as waterfall, spiral, agile etc. It then covers the specific phases in more detail - preliminary analysis, system analysis, design, development, integration and testing, acceptance and deployment, maintenance. Lastly, it discusses system requirement specification, including UML notations, diagrams to be used and provides a brief overview of class diagrams.
Anup Kumar Saha is seeking a challenging career in software development. He has over 8 years of experience in teaching and software development using technologies like Java, Spring, Hibernate, Oracle, and more. His experience includes roles at Cognizant, HCL Technologies, Ericsson, TCS, and others working on projects in various domains for clients like Airtel, GM, and others. He is currently an Assistant Professor but seeking new opportunities.
IRJET - A Review on Chatbot Design and Implementation TechniquesIRJET Journal
This document reviews techniques for designing and implementing chatbots. It discusses past works on chatbot design using techniques like neural machine translation and reinforcement learning. The document proposes developing a state-of-the-art chatbot using tools like DialogFlow, TensorFlow, Android Studio and Firebase, along with machine learning and deep learning techniques. It reviews papers on chatbot design and discusses their strengths, limitations, and potential for further improvement.
Md. Mashiur Rahman is seeking a full-time position in IT with an expected salary of 30,000 Taka. He has a Bachelor's degree in Electronics and Telecommunications Engineering and over 3 years of experience as a Senior IT Executive and IT Officer. His experience includes managing networking equipment, providing IT support, software maintenance, and developing websites. He is proficient in technologies like PHP, MySQL, and has strong communication and problem-solving skills.
The document provides details of a proposed mobile application called "Time Table & Event Reminder App" that allows users to set reminders for events like lectures or meetings. It includes an entity relationship diagram and class diagram that model the database structure, as well as use case, sequence, and collaboration diagrams that describe the interactions between users and the app. The app would allow both students and teachers to view schedules and set reminders for lectures, and also include a general reminder feature for other events.
The document provides an overview of a software engineering course syllabus and objectives. The syllabus covers 6 units: software process and agile development, requirements analysis and specification, object oriented concepts, software design, testing and management, and learning resources. The course objectives are to understand software project phases, requirements engineering, object oriented concepts, enterprise integration, and testing/project management techniques. Students will learn to compare process models, formulate requirements engineering concepts, understand object oriented fundamentals, apply software design procedures, and evaluate testing techniques and project schedules.
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.
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 an approach for automatically generating software artifacts and models from natural language requirements documents during the analysis phase of software development.
It proposes a technique that first converts the natural language into a formal Semantic Business Vocabulary and Rules (SBVR) format. It then performs semantic and syntactic analysis on the SBVR to identify software artifacts like actors, use cases, classes, attributes, methods, and relationships. These artifacts are used to generate analysis models like use case diagrams and class diagrams. Finally, it produces XML Metadata Interchange (XMI) files to visualize the generated models in a UML modeling tool. The goal is to increase accuracy over existing tools by using the SBVR intermediate representation and generating multiple analysis models rather
The document discusses an approach for automatically generating software artifacts and models from natural language requirements documents during the analysis phase of software development.
It proposes a technique that first converts the natural language into a formal intermediate representation using Semantic Business Vocabulary and Rules (SBVR) to improve accuracy. It then identifies software artifacts like actors, use cases, classes, attributes, methods, and relationships.
The technique generates UML analysis models like use case and class diagrams. It also produces XML Metadata Interchange (XMI) files to visualize the generated models in UML modeling tools that support XMI import. The goal is to help automate parts of the analysis phase and address limitations of existing tools in terms of coverage and accuracy
Generating requirements analysis models from textual requiremenfortes
This document describes a process for generating use case models from textual requirements. The process uses the EA-Miner tool to analyze textual requirements and extract information like functional concerns, RDL sentences, and a syntactically tagged document. This extracted information is used to derive initial candidate use cases, actors, and relationships. The candidate model is then refined by activities like removing undesirable use cases, completing abstraction names, adding new use cases/actors, and defining relationships between use cases. The overall goal is to reduce the time and effort required to produce requirements artifacts from textual specifications.
Local Service Search Engine Management System LSSEMSYogeshIJTSRD
Local Services Search Engine Management System LSSEMS is a web based application which helps user to find serviceman in a local area such as maid, tuition teacher, plumber etc. LSSEMS contain data of serviceman maid, tuition teacher, plumber etc. . The main purpose of LSSEMS is to systematically record, store and update the serviceman records. Kaushik Mishra | Aditya Sharma | Mohak Gund "Local Service Search Engine Management System (LSSEMS)" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Special Issue | International Conference on Advances in Engineering, Science and Technology - 2021 , May 2021, URL: https://www.ijtsrd.com/papers/ijtsrd42462.pdf Paper URL : https://www.ijtsrd.com/engineering/computer-engineering/42462/local-service-search-engine-management-system-lssems/kaushik-mishra
IRJET - Voice based Natural Language Query ProcessingIRJET Journal
This document describes a voice-based natural language query processing system that allows non-expert users to interact with a database using natural language queries. The system takes a user's spoken query as input, converts it to text using speech recognition, analyzes the text to generate a SQL query, executes the SQL query against the database, and displays the results in a table. The system addresses challenges like ambiguity through techniques such as tokenization, lexical analysis, syntactic analysis, and semantic analysis to map the natural language query to a valid SQL query.
Text Summarization and Conversion of Speech to TextIRJET Journal
This document discusses text summarization and speech to text conversion using deep learning algorithms. It describes how recurrent neural networks can be used for text summarization by identifying key information and semantic meaning from text. Speech recognition uses similar deep learning methods to convert spoken audio to text. The document also provides an overview of the text summarization process, including segmentation, normalization, feature extraction, and modeling steps. It concludes that these models can generate summarized text from extensive documents and meetings.
Presentation: Tool Support for Essential Use Cases to Better Capture Software...Naelah AlAgeel
The paper discusses developing a tool to help requirements engineers extract essential use cases (EUCs) from natural language requirements documents. The tool uses a library of abstract interaction patterns to automatically trace phrases in requirements documents and suggest EUCs. An evaluation found the tool was more accurate and faster than manual extraction. While users found the tool easy to use, they wanted more domain coverage and a better interface. The paper aims to overcome challenges in adopting EUCs by providing automated tool support to extract the correct essential interactions from requirements.
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.
A FRAMEWORK STUDIO FOR COMPONENT REUSABILITYcscpconf
The deployment of a software product requires considerable amount of time and effort. In order
to increase the productivity of the software products, reusability strategies were proposed in the
literature. However effective reuse is still a challenging issue. This paper presents a framework
studio for effective components reusability which provides the selection of components from framework studio and generation of source code based on stakeholders needs. The framework studio is implemented using swings which are integrated onto the Net Beans IDE which help in faster generation of the source code.
This document introduces object-oriented programming (OOP). It discusses the software crisis and need for new approaches like OOP. The key concepts of OOP like objects, classes, encapsulation, inheritance and polymorphism are explained. Benefits of OOP like reusability, extensibility and managing complexity are outlined. Real-time systems, simulation, databases and AI are examples of promising applications of OOP. The document was presented by Prof. Dipak R Raut at International Institute of Information Technology, Pune.
A Metamodel and Graphical Syntax for NS-2 ProgramingEditor IJCATR
One of the most important issues, around the world, which manufacturers pay special attention to is to promote their
activities in order to be able to give high quality products or services. Perhaps the first advice to achieve this goal is simulation idea.
Therefore, simulation software packages with different properties have been made available. One of the most applicable simulators is
NS-2 which suffers from internal complexity. On the other hand, Domain Specific Modeling Languages can make an abstraction level
by which we can overcome the complexity of NS-2, increase the production speed, and promote efficiency. So, in this paper, we
introduce a Domain Specific Metamodel for NS-2.This new metamodel paves the ways for introducing abstract syntax and modeling
language syntax. In addition, created syntax in Domain Specific Modeling Language is supported by a graphical modeling tool.
The document discusses key concepts in software design including abstraction, architecture, patterns, modularity, coupling and cohesion, and information hiding. It defines software design as transforming user requirements into an implementable form using programming languages. The software design process exists between requirements and programming and yields architectural, high-level, and detailed designs. It also outlines characteristics of good design like correctness, efficiency, and understandability.
IRJET- Factoid Question and Answering SystemIRJET Journal
This document describes a factoid question answering system that uses neural networks and the Tensorflow framework. The system takes in a text document and question as input. It then processes the input using techniques like gated recurrent units and support vector machines to classify the question. The system calculates attention between facts and the question, modifies its memory, and identifies the word closest to the answer to output as the response. Key aspects of the system include training a question answering engine with Tensorflow, storing and retrieving data, and generating the final answer.
Object Oriented Approach for Software DevelopmentRishabh Soni
This document provides an overview of object-oriented design methodologies. It discusses key object-oriented concepts like abstraction, encapsulation, and polymorphism. It also describes the three main models used in object-oriented analysis: the object model, dynamic model, and functional model. Finally, it outlines the typical stages of the object-oriented development life cycle, including system conception, analysis, system design, class design, and implementation.
This document provides an introduction and overview of the Stat project, which aims to create an open source machine learning framework in Java for text analysis. The Stat framework is designed to be simple, extensible, and performant. It aims to simplify common text analysis tasks for researchers and engineers by providing reusable tools and wrappers for existing NLP and machine learning packages. The document outlines the goals, scope, stakeholders and provides an initial requirements analysis for the Stat framework.
Class Diagram Extraction from Textual Requirements Using NLP Techniquesiosrjce
IOSR Journal of Computer Engineering (IOSR-JCE) is a double blind peer reviewed International Journal that provides rapid publication (within a month) of articles in all areas of computer engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in computer technology. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
This document presents a new method for extracting class diagrams from textual requirements using natural language processing (NLP) techniques. It proposes the Requirements Analysis and Class diagram Extraction (RACE) system, which uses tools like the OpenNLP parser, a stemming algorithm, and WordNet to extract concepts and identify classes, attributes and relationships. The RACE system applies heuristic rules and a domain ontology to the output of the NLP tools to refine and finalize the extracted class diagram. The paper concludes that the RACE system demonstrates the effective use of NLP techniques to automate the extraction of class diagrams from informal natural language requirements specifications.
Visual Programming and Program Visualization – Towards an Ideal Visual Softwa...IDES Editor
There has been a great interest recently in systems
that use graphics to aid in the programming, debugging, and
understanding of computer systems. The ‘’Visual
Programming’’ and ‘’Program Visualization’’ are exciting
areas of active computer science research that show promise
for improving the programming process, for this they have
been applied to these systems. This article attempts to provide
more meaning to these terms by giving precise definitions,
and then surveys a number of systems that can be classified as
providing Visual Programming or Program Visualization.
These systems are organized by classifying them into two
different taxonomies. The paper also gives a brief description
of our approach that concentrated on both Visual Programming
and Program Visualization for an Ideal Visual Software
Engineering System. We consider it as a new promising trend
in software engineering.
The News Today 24 (https://thenewstoday24.com/)IT Industry
The News Today 24 is source of latest and up-to-date information from all fields of life including politics, business, technology, entertainment and all other fields of life. For more detail, visit: https://thenewstoday24.com/
Imran Sarwar Bajwa, [2010], "Context Based Meaning Extraction by Means of Markov Logic", in International Journal of Computer Theory and Engineering - (IJCTE) 2(1) pp:35-38, February 2010
The document describes a system that can automatically generate SQL queries from natural language input. It discusses how the system works in multiple phases: it first acquires text input, then analyzes the text to comprehend it and extract necessary information like table names and conditions. It then generates the SQL queries based on this extracted information and predefined rules. The system was tested on sample queries and showed 80-90% accuracy in generating simple and complex queries for operations like select, insert and delete. While accurate, the authors note room for improving the algorithms to achieve higher than 85% accuracy and handle more types of queries.
Imran Sarwar Bajwa, [2010], "Virtual Telemedicine Using Natural Language Processing", International Journal of Information Technology and Web Engineering IJITWE 5(1):43-55, January 2010
Imran Sarwar Bajwa, Behzad Bordbar, Mark G. Lee. [2010] "OCL Constraints Generation from Natural Language Specification", in proceedings of EDOC 2010 - IEEE International EDOC Conference 2010, Vitoria, Brazil, Oct 2010, pp:204-213
BPM & SOA for Small Business Enterprises (ICIME 2009)IT Industry
Imran Sarwar Bajwa, S. Mumtaz, A. Samad, R. Kazmi, A. Choudhary [2009], "BPM meeting with SOA: A Customized Solution for Small Business Enterprises", in proceedings of IEEE- International Conference on Information management & Engineering 2009, Kuala Lumpur Malaysia, Apr 2009, pp:677-682
Imran Sarwar Bajwa, A. H. S. Bukhari, [2006] "Speech Language based Engineering System for Automatic Generation of User Forms", in International Conference on Man-Machine Systems (ICOMMS 2006), Kangar, Malaysia
Imran Sarwar Bajwa, M. Abbas Choudhry [2006], "A Study for Prediction of Minerals in Rock Images using Back Propagation Neural Networks", in IEEE 1st International Conference on Advances in Space Technologies (ICAST 2006), Aug 2006, Islamabad, Pakistan. pp:185-189
Imran Sarwar Bajwa, Irfan Hyder, M. Abbas Choudhary. [2006], “Suitable Reusable Components Mining to Assist Developers using a Rule Based System”, in Fifth International Conference on Information and Management Sciences (IMS 2006), Chengdu, China, Volume: 5 pp:266-270
M. Kashif Nazir, Imran Sarwar Bajwa, M. Imran Khan [2006], "A Conceptual Framework of Earthquake Disaster Management System (EDMS) for Quetta City using GIS", in IEEE 1st International Conference on Advances in Space Technologies, (ICAST 2006), Islamabad, Pakistan, Aug 2006, pp:117-120
Imran Sarwar Bajwa, M. Abbas Choudhary [2006], "A Rule Based System for Speech Language Context Understanding", International Journal of Donghua University (English Edition), Jun 2006, Vol. 23 No. 06, pp:39-42
Imran Sarwar Bajwa, S. Irfan Hyder [2005], "PCA Based Image Classification of Single-Layered Cloud Types", in 1st IEEE International Conference on Emerging Technologies (ICET 2005), Islamabad, Pakistan, Jan 2005, pp:365-369
Feature Based Image Classification by using Principal Component AnalysisIT Industry
Classification of different types of cloud images is the primary issue used to forecast precipitation and other weather constituents. A PCA based classification system has been presented in this paper to classify the different types of single-layered and multi-layered clouds. Principal Component Analysis (PCA) provides enhanced accuracy in features based image identification and classification as compared to other techniques. PCA is a feature based classification technique that is characteristically used for image recognition. PCA is based on principal features of an image and these features discreetly represent an image. The used approach in this research uses the principal features of an image to identify different cloud image types with better accuracy. A classifier system has also been designed to exhibit this enhancement. The designed system reads features of gray-level images to create an image space. This image space is used for classification of images. In testing phase, a new cloud image is classified by comparing it with the specified image space using the PCA algorithm.
Feature Based Image Classification by using Principal Component Analysis
UCD Generator (ICIET 2007)
1. IEEE- International Conference on Information and Emerging Technologies-
IEE-ICIET,
Karachi, Pakistan
UCD-Generator – A LESSA Application for Use Case Design
Imran S. Bajwa1, Irfan Hyder 2
1 CISUC – Departament of Informatics Engineering, University of Coimbra,
3030 Coimbra, Portugal
2- PAF-KIET
Karachi, Pakistan.
imran@dei.uc.pt, hyder@pafkiet.edu.pk
Abstract with the end user or another system to achieve a specific
business goal. Use cases are a tool for capturing
In object-oriented design, use cases are one of the functional requirements related to a designed system
important but complex components to design. UCD- applications. The functional requirements principally
Generator is a LESSA based application that makes this represent the intended behavior of a system. This
process more simple and easy. UCD-Generator is an complementary behavior may be expressed as services,
automated system that has vigorous ability to directly tasks or functions provided by the specific system [2].
interact wit the user. This research paper presents a The patterns of modeling and mapping of business logic
natural language processing based approach LESSA in software engineering have been completely changed
that is used for automatically understanding the natural in the recent times. These days all major phases of
language text and extract required information. This software engineering follow the rules defined by the
information is used to draw the Use Case diagrams. Object Oriented design paradigm. All phases of software
User writes his interface based preferences in simple engineering are deviating from the conventions and new
English in a few paragraphs and the designed system paradigms are more popular these days [3]. Same the
has conspicuous ability to analyze the given script. After case is with Software analysis process which uses
compound analysis and extraction of associated Unified Modeling Language to map and model the user
information, the designed system actually draws the Use requirements. Analysis is the key process of building
Case class diagrams. Other conventional CASE tools modern information system applications and base for the
require a complete understanding of the intended robust and vigorous software application’s design and
business scenario and lot of extra time and efforts from development.
the system analyst during the process of creating,
arranging, labeling and finishing the USE Case Use case design is the major part of UML
diagrams. The designed system provides a quick and documentation and is also a difficult phase of object
reliable way to generate Use Case diagrams to save the oriented design of software applications as use cases are
time and budget of both the user and system analyst. typically generated according to the requirements and
preferences of a particular user. A system analyst has to
spend a lot of time in correspondence with the user and
Keywords: Information Extraction, Use Case Design, understand his specific preferences. The other problem
Natural Language Processing, Automatic Diagrams specifically addressed in this research is software
Generation, Text Understanding, UML Diagrams. analysis and design using available CASE tools which
are just paint like tools as Visual UML, GD Pro, Smart
1. Introduction Draw, Rational Rose etc [5]. To use their extensively
overloaded interface of these CASE tools is a vexing
UML (Unified Modeling Language) provide several problem. The process of generating the UML diagrams
types of diagrams that are used to increase the simplicity through these software engineering tools is very
and conception of an application under development. difficult, time consuming and lengthy process to
Use case diagrams are one of the UML diagrams. A use perform. Consequently, an automated software
case diagram is used to exemplify the supported development was required that may acquire the
functionalities the system. The software development preference directly from user and generate
teams visualize the functional requirements of a system corresponding USE Cases with improved output in
by use case diagrams. A use case diagram describes the minimum time consumed.
relationship of the actors to main processes in the system
and also the relationships among different use cases. An In this paper, a natural language processing approach
actor is a human being that interacts with the designed is presented for semantic analysis of the text and its
system [1]. Each use case provides one or more conversion of text into the use case diagrams. The
scenarios that convey how the system should interact module that implements UCD-Generator is called
2. IEEE- International Conference on Information and Emerging Technologies-
IEE-ICIET,
Karachi, Pakistan
LESSA (Language Engineering System for Semantic adjectives and various other complements. It is little
Analysis). LESSA is an automated rule-based Approach complex and multipart procedure.
that reads the natural language text, understands its
A procedure is defined that understands these
meanings and extracts the required information. LESSA
sentences and discover the actor, finds interaction, goals
performs lexical, syntax and semantic analysis of the
and intended objects as following:
natural language text.
Actor: The actor causes the action to occur as in "user
In the next section the, the basics of LESSA have been
fills the form" user is actor who performs the task
briefly described. In the next section, the processing
of form filling.
steps of the UCD-Generator system have been
illustrated. In the next section, some experiments have Action: This component defines the ultimate goal of a
been illustrated and in the last section the used approach certain use case. For example, user fills form to
is compared with other used approaches for text get registered. Here registered is goal of the
understanding and furthermore the conclusion of the intended Use Case.
research has been illustrated.
Object: The thematic object is the object the sentence is
really all about— typically the object, undergoing
2. Proposed Approach a change. Often the thematic object is the same as
the syntactic direct object, as "User presses the
In order to address the intended problem of this
key." Here the key is thematic object.
research a useful and supportive system was required,
which has sound ability to facilitate and assist both the 2.2. LESSA
users and software engineers. The functionality of the
conducted research was domain specific but it can be LESSA (Language Engineering Systems for Semantic
enhanced easily in the future according to the Analysis) is a natural language processing approach.
requirements. Current designed system incorporate the That is primarily used to understand and analyze the
capability of understanding the mapping user natural language text. LESSA is based on a rule-based
preferences after reading the given business scenario in algorithm. This rule-based algorithm has a number of
plain text and then ultimately drawing the Use Case rules that are defined according to the English grammar.
diagrams. An Integrated Development Environment has LESSA bases on a rule based algorithm that is used for
also been provided for User Interaction and efficient understanding and analyzing the natural languages text.
Input and output. LESSA has following major modules:
2.1. Automated Object-Oriented Design 2.2.1. Tokenization
From various projected phases of software application This module reads the natural language text and
engineering, analysis and design of an information converts the text into lexical tokens. These lexical tokens
system actually relates to understand the system and its are processing elements of LESSA. These lexical tokens
primary components [2]. Typically, design relates to are further passed to the next phase for further
manage and control the complexity parameter in a processing.
domain. In software engineering, design methods
provide various notation usually graphical ones. These 2.2.2. POS Tagging
notations allow to store and communicate the perpetual
design decisions. Object-oriented design has overruled This module receives the lexical tokens from the
the typical analysis and design techniques as structured previous module and applies a rule-based algorithm on
design and data-driven design [5]. As compared to old the text. The major function of this module is to identify
style design paradigms, object-oriented design models and extract the various parts of speech in the given text.
the every active entity of the problem domain using This phase is also called parts of speech tagging [13].
concept of objects. Objects have:
2.2.3. Meaning Understanding
– Object State (shape and condition)
This last module understands the semantics of the
– Object Behaviour (What they perform) given test and on the basis of extracted semantics, the
The major emphasis of the conducted research was object, subject and adverb parts of the sentences are
automatic identification of objects from a problem identified. Following is an example to describe the
domain. User provides the input text in English language working of LESSA module.
related to the business domain. After the lexical analysis "User fills the form."
of the text, syntax analysis is performed on word level to
recognize the word category [6]. First of all the available Typically, LESSA reads this text and performs the
lexicons are categorized into nouns, pronouns, lexical analysis to find the parts of speech and then
prepositions, adverbs, articles, conjunctions, etc. The further analyze to find the actor, action and the object in
syntactic analysis of the programs would have to be in a the given course of text. For this example, following is
position to isolate subject, verbs, objects, adverbs, the output.
3. IEEE- International Conference on Information and Emerging Technologies-
IEE-ICIET,
Karachi, Pakistan
Lexicons Phase-I Phase –II Step 3 – In this step, particular actions of an actor
with the system are defined. These are the actions that
User Noun Actor are required by an actor and these actions in a system are
fills Verb Action categorized as Use Cases.
the Article -------
form Noun Object Step 4 - For each of these Use Cases decide on the
most usual course when that Actor is using the system.
This is the final output of syntax assessment phase and This is the basic course or description of the Use Case.
all subject nouns are marked as objects and verbs are
marked as actions and all object nouns s are marked as
the objects in the scenario. In the above example, there is Fills the form
one actor ‘User’ in the example. Besides the actor, there
is also an action ‘fills’ and finally there is an object
“form”, on which certain action has been performed. User
Figure 3.2 – Generating a complete Use Case
3. UCD-Generator
The designed system UCD-Generator (Use case 3.3. UCD-Generator Architecture
Diagram Generator) uses natural language processing
techniques to generate the Use Case diagrams. The The complete architecture of UCD-Generator has been
process of generation of the use case diagram is a multi- divided into three distinct parts. First part The natural
phase process. There are two main phases as following language processing engine is module which performs
lexical and syntax analysis and extracts information like
a. Information Extraction who is actor, what is an object and what is the related
b. Diagram Generation description of the particular use case. The details are
manifested below:
3.1. Information Extraction
In the information extraction phase the text input
given by the user is analyzed to extract the parts of
speech. This phase is also called parts of speech tagging
in which pronouns, verbs, adjectives, articles, etc are
identified in a sentence. LESSA performs this action that
typically uses a rule-based algorithm that has been used
to perform syntax analysis. After Syntax analysis, the
sentence level categorization of a sentence (string) as
actor, object is performed. In the last the categorized
string of a sentence is represented in to the respective
Use Case diagrams
3.2. Diagram Generation
In this phase, first the extracted information from the
previous phase is analyzed and then according to this
information, the use case diagrams are generated. In this
phase, small diagrams are combined to generate the
complete use case diagram. The designed system follows
following four steps to generate a use case diagram.
Step 1 – In step I, the actors are identified. Actors
are those people who use the various functions of the
intended system e.g. “User hits the key”. Here the actor
is represented by the user
Step 2 – One Actor is picked at a time. Actor is
named: actor is named “user” in this example.
Figure 3.3 - Describe the Basic Course for each Use Case
The designed system has an insightful ability to
User
understand the natural language text and draw the
Figure 3.1 – Actor in a Use Case intended use case diagrams. Current designed system
4. IEEE- International Conference on Information and Emerging Technologies-
IEE-ICIET,
Karachi, Pakistan
incorporate the capability of understanding the mapping
user preferences after reading the given business
scenario in plain text and then ultimately drawing the
Use Case diagrams. An Integrated Development
Environment has also been provided for User Interaction
and efficient Input and output.
4. Experiments and Analysis
An application UCD-Generator was designed to test
the results of the proposed approach. This application
has two parts. First part is the input acquisition part in
which an input window is available. Input text can be
provided here for further processing as shown in the
Figure 4.2 – Use Case Information Dialog Box
figure 4.1.
The use case information is displayed in the ‘Use Case
View’ window. This window has two abs. The ‘Use
Cases’ tab shows the generated use cases. Other tab ‘Use
Case Info’ shows the extracted information from the
input text. The information available is the use case
actor, use case action and use case object. After
extracting this information, a use case diagram can be
generated successfully.
Figure 4.3 shows the final output window which
displays the generated use case in ‘Use Case’ window.
The generated use case is based on the information
displayed in the ‘Use Case Info.’ window. An additional
facility is provided for the user of the system, that he can
modify the extracted information for accurate use case
diagram generation. User can select the accurate
information from ‘UseCase Info’ tab to improve the
accuracy.
Figure 4.1 – Use Case Input Dialog Box
The input dialog box of UCD-Generator has two tabs.
First tab is ‘UseCase Input’ and second tab is ‘Samples’.
In first tab common tips to generate the system use cases
are provided. For better accuracy, user is intended to
write only one or two use cases at a time. User is also
expected tow write grammatically correct English as this
will finally enhance the system accuracy. The complete
information about any use case should be provided:
actor, action and action description. In ‘UseCase Input’
window ‘Scenario Help’ is also provided for assisting
the user in providing precise input. ‘Sample’ tab has
some sample examples of input and their generated
output by the UCD-Generator.
Figure 4.3 – Use Case final Output Dialog Box
In this example the input text was “First, the user fills
the form. Then he submits the form further processing.” User can improve the diagrams accuracy by repeating
In this input there are two use cases of single this process with technically and grammatically
functionality. When the user clicks the ‘Draw Diagram’ improved input text. About 50 different real-time
button, the text is handed over to LESSA for semantic scenarios were provided to the system to check its
analysis. LESSA module first reads the input text and accuracy. 85% of the scenarios were accurately
converts the text into lexical tokens. These tokens are translated into use case diagram. Accuracy if further
further processed to find the parts of speech. After parts- improves if the extracted information is filtered before
of-Speech tagging, the text is further analyzed to extract generating the diagrams.
its meanings. The extracted information is shown in the
figure 4.2.
5. IEEE- International Conference on Information and Emerging Technologies-
IEE-ICIET,
Karachi, Pakistan
5. CONCLUSION American Society for Information Science, 39(1), 1988,
pp. 8–16.
This conducted research is all about the automatic
generation of the Use Case diagrams after reading and [11] S. Kok and P. Domingos, (2005) “Learning the structure
of Markov logic networks’, In Proc. of ICML-05, Bonn,
analyzing the given scenario in English language Germany, 2005. ACM Pres, pp 441–448
provided by the user. The designed system can find out
the classes and objects and their attributes and operations [12] S. Kok, P. Singla, M. Richardson, and P. Domingos,
using an artificial intelligence technique such as natural (2005) “The Alchemy system for statistical relational
language processing. Then the Use Case diagrams are AI”, Technical report, Department of Computer Science
drawn. The accuracy of the software is up to about 85% and Engineering, http://www.-cs.washington.edu/ai/
with the involvement of the software engineer provided alchemy.
that input is properly formatted. The given scenario [13] Imran Sarwar Bajwa, M. Abbas Choudhary, (2006) “A
should be complete and written in simple and correct Rule Based System for Speech Language Context
English. Under the scope of our project, software will Understanding” Journal of Donghua University, (English
perform a complete analysis of the scenario to find the Edition) 23 (6), pp. 39-42.
classes, their attributes and operations. A well-designed [14] Burns, J., & Madey, G. (2001), “A framework for
graphical user interface has also been provided to the effective user interface design for web-based electronic
user for entering the Input scenario in a proper way and commerce applications”, Informing Science, 4 (2), 67-75
generating Use Case diagrams to ultimately make them
the part of the object oriented documentation. [15] Woo, H., & Robinson, W. (2002). “A light-weight
approach to the reuse of use-cases specifications”, In
Proceedings of the 5th annual conference of the Southern
REFERENCES Association for Information Systems (pp. 330- 336)
Savannah: SAIS
[1] Anda, B., Sjøberg, D., and Jørgensen, M. “Quality and
Understandability in Use Case Models” In Proc. 13th [16] Malaisé Véronique, Zweigen. Pierre, Bachimont Bruno,
European Conference on Object-Oriented Programming (2005) “Mining Defining Contexts to Help Structuring
(ECOOP'2001), Jørgen Lindskov Knudsen (editor), June Differential Ontologies”, Terminology, 11:1
18-22 2001, Budapest, Hungary, LNCS 2072, Springer
Verlag, pp. 402-428.
[17] Imran Sarwar Bajwa, Riaz-Ul-Amin, M. Asif Naeem,
Muhammad Nawaz (2006), “Web Information Mining
[2] Ruth Malan and Dana Bredemeyer, (2001) “Functional Framework using XML Based Knowledge
Requirements and Use Cases”, Bredemeyer Consulting, Representation Engine, Proceedings of 2nd International
ruth_malan@bredemeyer.com Conference on Software Engineering, 2006, Lahore,
Pakistan
[3] Imran Sarwar Bajwa, M. Abbas Choudhary (2006), “A
Language Engineering System for Automatic [18] Condamines, Anne and Rebeyrolle, Josette. (2001).
Conversion of English Cyber Data into Urdu Websites”, “Searching for and identifying conceptual relationships
Proceedings of International Conference on Computer via a corpus based approach to a Terminological
Applications 2006, Yangoon, Myanmar Knowledge Base (CTKB): Method and Results”, Recent
Advances in Computational Terminology, pp. 127-148
[4] Imran Sarwar Bajwa, M. Abbas Choudhary (2006),
“Speech Language context understanding using a Rule [19] Imran Sarwar Bajwa, M. Abbas Choudhary (2006), “A
Based Framework”, International Conference on Language Engineering System for Graphical User
Intelligent Systems and Knowledge Engineering, Interface Design (LESGUID): A Rule based Approach”,
Shanghai, China Proceedings of IEEE- 2nd International Conferences on
Information & Communication Technologies,
[5] Chomsky, N. (1965) “Aspects of the Theory of Syntax. Damascus, Syria
MIT Press, Cambridge, Mass, 1965.
[20] L. R. Tang and R. J. Mooney, (2001), “Using Multiple
[6] Chow, C., & Liu, C. (1968) “Approximating discrete Clause Constructors in Inductive Logic Programming for
probability distributions with dependence trees”. IEEE Semantic Parsing”, Proceedings of the 12th European
Transactions on Information Theory, 1968, IT-14(3), Conference on Machine Learning (ECML- 2001),
462–467. Freiburg, Germany, pages 466–477.
[7] Krovetz, R., & Croft, W. B. (1992) “Lexical ambiguity [21] Drouin Patrick. (2004). “Detection of Domain Specific
and information retrieval”, ACM Transactions on Terminology Using Corpora Comparison” Proceedings
Information Systems, 10, 1992, pp. 115–141 of the Fourth International Conference on Language
Resources and Evaluation (LREC), Lisbon, Portugal
[8] Salton, G., & McGill, M. (1995) “Introduction to
Modern Information Retrieval” McGraw-Hill, New [22] J. M. Zelle and R. J. Mooney, (1993), “Learning
York., 1995 semantic grammars with constructive inductive logic
programming”, in: Proceedings of the 11th National
[9] Maron, M. E. & Kuhns, J. L. (1997) “On relevance,
Conference on Artificial Intelligence (AAAI Press/MIT
probabilistic indexing, and information retrieval” Journal
Press, Washington, D.C.) , pp. 817–822.
of the ACM, 1997, 7, 216–244.
[10] Losee, R. M. (1988) “Parameter estimation for [23] Khoo Christopher, Chan Syin, Niu Yun, (2002) “The
Many Facets of the Cause-Effect Relation”, The
probabilistic document retrieval models”. Journal of the
6. IEEE- International Conference on Information and Emerging Technologies-
IEE-ICIET,
Karachi, Pakistan
Semantics of Relationships. Kluwer Academic Press. pp.
51-70
[24] Gómez-Pérez Asunción, F. Mariano, C. Oscar, (2004)
“Ontological Engineering: with examples from the areas
of Knowledge Management”, e-Commerce and the
Semantic Web. Springer