Relation.....too fundamental to be ill-defined but is it well defined? Is it useful? Not quite according to me. I have my questions and reasons to redefine relation radically. Here is the proposal.
Framework for Online Software Evolution FOSE 04AUG22.pdfPutcha Narasimham
Framework for Online Software Evolution: FOSE
Abstract
Business Application Software BAS malfunctions often during early stages of development and deployment. They are inevitable and unavoidable. They are costly and time consuming to fix. There are two kinds of errors that cause BAS malfunction, (1) Errors in Business Policies, Rules, Information and Data (2) Software Errors of BAS. It is here proposed that some means of quick and safe correction and relaunching process be built into software design and operation. There are two separate proposals for (1) and (2). The second is discussed here.
ASIS (current) Process Map shows BAS running on its platform with its actors. The software development system (CI/CD Server) with BAS Developers is NOT connected to BAS or actors of BAS. The proposed Framework for Online Software Evolution FOSE is added to interconnect BAS Developer, CI/CD Server, and Platform of BAS online (while running).
Business Actor of BAS initiates Software Correction Request and online Business Authority (specially added actor of BAS) approves it for transmission to FOSE. Approved Software Correction Requests flow from BAS to FOSE and FOSE to BAS Developer. The BAS Developer then identifies the affected parts of BAS that need correction and works on the source code of BAS available in CI/CD Server. Then he or she corrects parts of BAS and tests them to generate a corrected trial version of BAS. The corrected trial version of BAS is available to the end users of BAS for evaluation of how their requests have been processed and met. The corrected and tested parts of BAS are then released to the Platform of BAS. The framework FOSE is notified of this for updating the status of approved software correction requests maintained in FOSE. Then FOSE allows launch of the new version of BAS. Making end users initiate “software correction requests”, approving them and passing them through FOSE to online BAS Developers in a closed loop, are the key factors for software evolution.
Thus, the BAS together with FOSE, becomes robust BAS continually. Here the software itself is Agile---not the software development. Incomplete software can safely be launched and run without frequent crashes. Unspecified user requirements get systemically captured from the business actors and met.
---III---
See examples and explanation in a separate word document
Normal Business Application Software BAS provides ONLY the business functionality, which is good enough if it works well. However that is never the case particularly for the new functionality offered for the first time. Invariably unforeseen business and software situations arise and the the BAS needs modifications often at design level of the business logic and or the BAS itself. All this has to be done off line. Here it is proposed that both Business Support and Software Development Support be brought ONLINE. Here the Application Software itself becomes AGILE in operation---NOT just the software development process.
This is facilitated by two radical design changes.
First, the BAS it self is restructured and designed to bring Business Authority ONLINE and set up a Business Policy and Rules Repository BPRR.
Second, an additional Framework for Online Software Evolution is provided to bring the BAS Developers and the software development system online.
See how the combination works in this and two supplementary PPTs.
Plan Anything personally or professionally. Planning is a preparation for the future with a GOAL for some one. I dentify all of them. There are two major branches: Resource Planning and Action Planning. Planning can be elaborate or simple. Select the factors for quick success of your mission. Drop what is not relevant but do not miss anything vital. Best wishes,
Machine mediated meaning for semantic interoperability pvn 120109 pdfPutcha Narasimham
1) The document proposes a definition of meaning as "the property of valid expression in Natural Language Text (NLT) along with the context, which is capable of generating “Predefined Responses (PreRes)” from a “Specified Class of Recipients (R)” and the “meaning of NLT for R is PreRes”."
2) It examines existing definitions of meaning from dictionaries and scholars and finds them insufficient for defining meaning that both humans and machines can understand.
3) The proposed definition explicitly includes the recipient (R) and predefined responses to determine the meaning generated in the recipient's mind from the text, in order to have an objective way to assess meaning without further interpretation.
Relation in set theory of math is flawed. It remains undetected and uncorrected even now. This 11 slide PPT point outs the errors with examples, corrects them, giving a better definition. It may be too elementary but how can math live with errors in fundamentals?
- The document proposes corrections to errors in use case modeling, defining a use case as a sequence of messages between a system and actor, similar to a BPMN conversation.
- It suggests use cases should be modeled externally to the system as hexagons or conversation elements, rather than internally as ovals. Actor should be an external entity rather than role.
- A use case can also be modeled as an association class in a class diagram, showing its relationship between an actor class and the system class.
Harmonizing use cases, dialogs or conversations, process maps, usecase diagra...Putcha Narasimham
UseCase concept is unique and profound concept to represent the needs of businesses and users from their view point. Based on UseCase and Actor identification, the System to be Developed can be specified and evolved systematically. This summary updates and integrates many proposals made earlier. It logically integrates all the concepts of the title.
How to study any publication deeply for analysis and research. The process and reporting format are presented with examples. This paves way for incremental discovery and innovation and validation / consolidation.
Framework for Online Software Evolution FOSE 04AUG22.pdfPutcha Narasimham
Framework for Online Software Evolution: FOSE
Abstract
Business Application Software BAS malfunctions often during early stages of development and deployment. They are inevitable and unavoidable. They are costly and time consuming to fix. There are two kinds of errors that cause BAS malfunction, (1) Errors in Business Policies, Rules, Information and Data (2) Software Errors of BAS. It is here proposed that some means of quick and safe correction and relaunching process be built into software design and operation. There are two separate proposals for (1) and (2). The second is discussed here.
ASIS (current) Process Map shows BAS running on its platform with its actors. The software development system (CI/CD Server) with BAS Developers is NOT connected to BAS or actors of BAS. The proposed Framework for Online Software Evolution FOSE is added to interconnect BAS Developer, CI/CD Server, and Platform of BAS online (while running).
Business Actor of BAS initiates Software Correction Request and online Business Authority (specially added actor of BAS) approves it for transmission to FOSE. Approved Software Correction Requests flow from BAS to FOSE and FOSE to BAS Developer. The BAS Developer then identifies the affected parts of BAS that need correction and works on the source code of BAS available in CI/CD Server. Then he or she corrects parts of BAS and tests them to generate a corrected trial version of BAS. The corrected trial version of BAS is available to the end users of BAS for evaluation of how their requests have been processed and met. The corrected and tested parts of BAS are then released to the Platform of BAS. The framework FOSE is notified of this for updating the status of approved software correction requests maintained in FOSE. Then FOSE allows launch of the new version of BAS. Making end users initiate “software correction requests”, approving them and passing them through FOSE to online BAS Developers in a closed loop, are the key factors for software evolution.
Thus, the BAS together with FOSE, becomes robust BAS continually. Here the software itself is Agile---not the software development. Incomplete software can safely be launched and run without frequent crashes. Unspecified user requirements get systemically captured from the business actors and met.
---III---
See examples and explanation in a separate word document
Normal Business Application Software BAS provides ONLY the business functionality, which is good enough if it works well. However that is never the case particularly for the new functionality offered for the first time. Invariably unforeseen business and software situations arise and the the BAS needs modifications often at design level of the business logic and or the BAS itself. All this has to be done off line. Here it is proposed that both Business Support and Software Development Support be brought ONLINE. Here the Application Software itself becomes AGILE in operation---NOT just the software development process.
This is facilitated by two radical design changes.
First, the BAS it self is restructured and designed to bring Business Authority ONLINE and set up a Business Policy and Rules Repository BPRR.
Second, an additional Framework for Online Software Evolution is provided to bring the BAS Developers and the software development system online.
See how the combination works in this and two supplementary PPTs.
Plan Anything personally or professionally. Planning is a preparation for the future with a GOAL for some one. I dentify all of them. There are two major branches: Resource Planning and Action Planning. Planning can be elaborate or simple. Select the factors for quick success of your mission. Drop what is not relevant but do not miss anything vital. Best wishes,
Machine mediated meaning for semantic interoperability pvn 120109 pdfPutcha Narasimham
1) The document proposes a definition of meaning as "the property of valid expression in Natural Language Text (NLT) along with the context, which is capable of generating “Predefined Responses (PreRes)” from a “Specified Class of Recipients (R)” and the “meaning of NLT for R is PreRes”."
2) It examines existing definitions of meaning from dictionaries and scholars and finds them insufficient for defining meaning that both humans and machines can understand.
3) The proposed definition explicitly includes the recipient (R) and predefined responses to determine the meaning generated in the recipient's mind from the text, in order to have an objective way to assess meaning without further interpretation.
Relation in set theory of math is flawed. It remains undetected and uncorrected even now. This 11 slide PPT point outs the errors with examples, corrects them, giving a better definition. It may be too elementary but how can math live with errors in fundamentals?
- The document proposes corrections to errors in use case modeling, defining a use case as a sequence of messages between a system and actor, similar to a BPMN conversation.
- It suggests use cases should be modeled externally to the system as hexagons or conversation elements, rather than internally as ovals. Actor should be an external entity rather than role.
- A use case can also be modeled as an association class in a class diagram, showing its relationship between an actor class and the system class.
Harmonizing use cases, dialogs or conversations, process maps, usecase diagra...Putcha Narasimham
UseCase concept is unique and profound concept to represent the needs of businesses and users from their view point. Based on UseCase and Actor identification, the System to be Developed can be specified and evolved systematically. This summary updates and integrates many proposals made earlier. It logically integrates all the concepts of the title.
How to study any publication deeply for analysis and research. The process and reporting format are presented with examples. This paves way for incremental discovery and innovation and validation / consolidation.
This document describes a Needs & Means Matrix for allocating resources (means) to meet needs and maximize benefits while minimizing costs. The matrix analyzes and ranks customer needs and available means to meet those needs. It then plots the needs and means in the matrix with correlation values representing how effectively a given mean can meet a particular need. This allows identification of high-value means that meet important needs cost-effectively as well as low-value means that should be eliminated or replaced. The matrix provides a systematic approach to design high value products and services.
Are there any generic tools to analyze and assess documents? Here are some suggestions including Procedure to Cluster Concepts & Check for their Coupling in a document.
I found it helpful. I suppose something like this or even better would be available.
Describing something new poses very serious problems. Dictionaries and encyclopedia have met this requirement fairly well but those methods and techniques are NOT within the reach of millions of us who have to "describe things or introduce things" for teaching, documenting, modeling for analysis and design etc.
Here is my proposal to do it with a simple table. Yes, it is derived from class definition and description of OOAD but it is very effective for use in general. See how it works and let's help millions of students and teachers who struggle to describe things. Here is a structure to it which solves 80% of the problem. Cheers!
Software is very special. I is grand, spectacular, regenerative and perpetual source of value---like nothing else we know.
Perhaps for this very reason it is misused and wasted. By cooperatively REUSING ALL ARTIFACTS of software, we can reap unheard of benefits repeatedly. Here is an outline of how we can do it. That is ReSAR. Let's start.
Multiple Actors DO interact with the SuC, which is why the SuC exists in the first place, but NO TWO of them can do so through a single UseCase. There can be NO Second Actor in a UseCase.
Each interaction, more appropriately the dialog, can only have two members actively involved in the dialog.
First is the SuC and the second is the associated Actor.
The nature of UseCase and its implications were well discussed in
http://www.slideshare.net/putchavn/usecase-case-is-a-dialog-not-a-process
http://www.slideshare.net/putchavn/use-casesingle-session
http://www.slideshare.net/putchavn/one-use-case-one-actor
Yet there are discussions and justifications for associating multiple actors with the same UseCase.
UseCase is a DIALOG involving only one SuC and One Actor per Session. There is NO scope for another actor to take part in that dialog. Here is an example ATM Cash withdrawal. It needs THREE separate UCs.
This is explained using Process Maps to show the separation and how to separate.
This should end the confusion and persistent misunderstanding and misrepresentation.
Combined UseCase Description, MockUp Screens & System Sequence DiagramPutcha Narasimham
There are different artifacts (documents) for Use Case Description, Mock-up Screens and System Sequence Diagram. That is because each UML diagram (or table or description, Use Case Description has no diagram) can accommodate only a few modeling elements.
Analysts often need a set of UML diagrams and descriptions to evolve and represent concepts. They have to be drawn quickly and iteratively to formulate and express the business concepts and requirements. They need to be created and edited together, not in isolation.
It is here claimed that the contents of these three UML artifacts can be combined into a single text-document with tables & without drawings.
This is a sequel to Pentagon of MEANING. Here we point out that what we generally accept as meaning of text is its most valid interpretation according to published grammar & vocabulary of the language.
Such meaning is arrived at by sharing and negotiation of the text and its interpretation / clarification etc.
The secret of reaching a common meaning is NOT long negotiation but it is: creating most unambiguous text. This is possible with the help of machine aided drafting of text.
This is the subject of full paper by the author "Machine Mediated Meaning for Semantic Interoperability" which will be uploaded shortly.
Please take a look and give your views.
Ogden and Richards published a full book "The Meaning of Meaning" in 1923. It is also a subject of a lot of research by a broad spectrum of scholars & scientists. But they have identified only 3 elements of meaning but we found FIVE. Hence, PENTAGON of Meaning moving from their TRIANGLE of Meaning.
The five elements are: Speaker S, Concept X in her mind, Text T to express X, Listener L, who creates Concept X' from T. Out of these only S, T and L are public, open for observation. The concepts X and X' are private separately to S and L and the meaning is X for S and X' for L. That is subject of this PPT. It is elaborated and discussed.
From here we need to arrive at common and open meaning of T. We have another PPT for that.
There is a full paper Machine Mediated Meaning for Semantic Interoperability, which you can find on slideshare soon.
Please leave a comment.
Concept Maps are very effective for language-free expression and communication of concepts visually. The fundamental structures, which are not all graphic, are also very elegant for encoding knowledge for machine processing.
The building blocks of knowledge (Nodes and Links) are NOT sufficiently "expressive & precise". HyperPlex fills this need. See the PPT by that name in https://www.slideshare.net/putchavn
Both the concepts are explained with examples.
Good for general use and a prerequisite for knowing what is knowledge and how to represent it. Leave a comment.
[1] A view that a UseCase (UC) is a "dialog" between the System under Consideration (SuC) and an Actor (for a specific UC) brings focus to what "messages need to be exchanged between the SuC and Actor to reach UC Goal".
[2] Agreeing on and specifying UC Goal is related to business or application. UC Goal would be the right first step of UC description.
[3] There are many "means" of generating "messages from SuC", through various internal activities within the SuC. They need not be (I would even say should not be) specified in UC Description.
[4] The concept of UseCase is profound and useful because it is a "dialog" but NOT a process. This distinction is not defined and clarified which is why, I think, the full benefits of UC modeling are not widely realized.
[5] This view of UC (as per 1, 2 & 3) clearly separates the "internal processes" of the SuC from UC. The "internal processes" can be hypothesized and evolved separately using UML Sequence Diagrams. All the business / user needs can be specified with sufficient precision and rigor through the “messages” of UC dialog. There are no external dependencies, though constraints may exist and have to be taken care of.
I have REVISED & uploaded the PPT with TWO Sections, Section 2 First.
[6] I would like to study applications and demonstrate how the "dialog" view of UseCase would simplify & clarify UseCase description for the business user as well as system developer without sacrificing precision and usefulness.
02 FEB 14
Returning part of output back to input is considered feedback but this is NOT valid in all cases. This identifies what is missing in a complete FEEDBACK model: The User or Customer of the output. The feedback must come from the User of the output based on using the output. What such user gives is TRUE feedback. Many cases in which feedback works effectively it is because the feedback is TRUE. Such cases are discussed to support this view.
Use this and let me know your cases and how you are using TRUE feedback.
BA and RE Coaching, Training, Teaching,through Quizzes, Assignments, Mini Projects. Learning by DOING with MINIMUM LECTURING
Short intense Single Module Courses....of 4 to 6 Sessions.
The document discusses process modeling and identifies six key elements of a comprehensive process representation: 1) inputs, 2) activities performed by a performer, 3) outputs, 4) process resources and consumables, 5) undesirable inputs and outputs, and 6) feedback in and out. It argues that effective process modeling requires representing all six elements, including distinguishing between physical and logical flows, performers, and incorporating feedback loops. The six element model provides a complete way to analyze, communicate, and design processes.
CONTEXT of Context of the System(s) to be DevelopedPutcha Narasimham
Context Diagram or Use Case Diagram are created directly without many principles or guidelines for the validity of them. Many implicit assumptions and informal designs come into play. There is a need for the CONTEXT of context. It is here pointed out that Explicit TO BE Process is very helpful to overcome the limitations to prepare and assure that CD or UCD is valid and reliable. Three examples are added in this revision. An 8 Process example is used to show the method. See how it helps. Let's discuss.
These are TQM Quality Improvements Methods and Tools adapted for BA and RE. They are simple but potent if used with deep understanding and commitment.
All the tools are not discussed. End-Means Tree is excellent for planning and innovation.
I have added a PPT of 50 slides. It gives diagrams which I have not been able to add to text in this PDF.
See the PPT by the same name at www.slideshare.net/putchavn
What is normally called feedback may not be TRUE FEEDBACK. There are conditions to be applied. Only then can one realize the benefits of feedback. This understanding is necessary to design effective business processes that involve machines and humans.
This is an extended abstract for helping interaction. Feel free to email kenablersys@yahoo.com
Context
There are several commercial and open source drawing tools. Some of them are integrated into word processing and presentation tools. Some are very advanced and sophisticated drawing and picturing systems. However, none of them are as quick and convenient as sketching & writing on paper or whiteboard.
The Need
So, there is a need for a drawing tool that is fast, flexible and easy-to-use as sketching & writing and yet is capable of producing high quality diagrams.
Normally Use Case Diagrams are used but the pictorial information in it is so small that an MS Word Table is sufficient. What is more it can also provide space for "Use Case Goal" which is very important for Use Case Modeling.
Tables are quick and easy to create and edit. No need to waste time to draw and label diagrams. One can still do it if necessary after creating the Use Case TABLE. Try.
A Use Case Table can spill over into multiple pages but a diagram cannot!
UML 2.5 allows TABLES to be used for diagrams. So, there is no compulsion to create diagrams spending a lot of time.
Main Java[All of the Base Concepts}.docxadhitya5119
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
This document describes a Needs & Means Matrix for allocating resources (means) to meet needs and maximize benefits while minimizing costs. The matrix analyzes and ranks customer needs and available means to meet those needs. It then plots the needs and means in the matrix with correlation values representing how effectively a given mean can meet a particular need. This allows identification of high-value means that meet important needs cost-effectively as well as low-value means that should be eliminated or replaced. The matrix provides a systematic approach to design high value products and services.
Are there any generic tools to analyze and assess documents? Here are some suggestions including Procedure to Cluster Concepts & Check for their Coupling in a document.
I found it helpful. I suppose something like this or even better would be available.
Describing something new poses very serious problems. Dictionaries and encyclopedia have met this requirement fairly well but those methods and techniques are NOT within the reach of millions of us who have to "describe things or introduce things" for teaching, documenting, modeling for analysis and design etc.
Here is my proposal to do it with a simple table. Yes, it is derived from class definition and description of OOAD but it is very effective for use in general. See how it works and let's help millions of students and teachers who struggle to describe things. Here is a structure to it which solves 80% of the problem. Cheers!
Software is very special. I is grand, spectacular, regenerative and perpetual source of value---like nothing else we know.
Perhaps for this very reason it is misused and wasted. By cooperatively REUSING ALL ARTIFACTS of software, we can reap unheard of benefits repeatedly. Here is an outline of how we can do it. That is ReSAR. Let's start.
Multiple Actors DO interact with the SuC, which is why the SuC exists in the first place, but NO TWO of them can do so through a single UseCase. There can be NO Second Actor in a UseCase.
Each interaction, more appropriately the dialog, can only have two members actively involved in the dialog.
First is the SuC and the second is the associated Actor.
The nature of UseCase and its implications were well discussed in
http://www.slideshare.net/putchavn/usecase-case-is-a-dialog-not-a-process
http://www.slideshare.net/putchavn/use-casesingle-session
http://www.slideshare.net/putchavn/one-use-case-one-actor
Yet there are discussions and justifications for associating multiple actors with the same UseCase.
UseCase is a DIALOG involving only one SuC and One Actor per Session. There is NO scope for another actor to take part in that dialog. Here is an example ATM Cash withdrawal. It needs THREE separate UCs.
This is explained using Process Maps to show the separation and how to separate.
This should end the confusion and persistent misunderstanding and misrepresentation.
Combined UseCase Description, MockUp Screens & System Sequence DiagramPutcha Narasimham
There are different artifacts (documents) for Use Case Description, Mock-up Screens and System Sequence Diagram. That is because each UML diagram (or table or description, Use Case Description has no diagram) can accommodate only a few modeling elements.
Analysts often need a set of UML diagrams and descriptions to evolve and represent concepts. They have to be drawn quickly and iteratively to formulate and express the business concepts and requirements. They need to be created and edited together, not in isolation.
It is here claimed that the contents of these three UML artifacts can be combined into a single text-document with tables & without drawings.
This is a sequel to Pentagon of MEANING. Here we point out that what we generally accept as meaning of text is its most valid interpretation according to published grammar & vocabulary of the language.
Such meaning is arrived at by sharing and negotiation of the text and its interpretation / clarification etc.
The secret of reaching a common meaning is NOT long negotiation but it is: creating most unambiguous text. This is possible with the help of machine aided drafting of text.
This is the subject of full paper by the author "Machine Mediated Meaning for Semantic Interoperability" which will be uploaded shortly.
Please take a look and give your views.
Ogden and Richards published a full book "The Meaning of Meaning" in 1923. It is also a subject of a lot of research by a broad spectrum of scholars & scientists. But they have identified only 3 elements of meaning but we found FIVE. Hence, PENTAGON of Meaning moving from their TRIANGLE of Meaning.
The five elements are: Speaker S, Concept X in her mind, Text T to express X, Listener L, who creates Concept X' from T. Out of these only S, T and L are public, open for observation. The concepts X and X' are private separately to S and L and the meaning is X for S and X' for L. That is subject of this PPT. It is elaborated and discussed.
From here we need to arrive at common and open meaning of T. We have another PPT for that.
There is a full paper Machine Mediated Meaning for Semantic Interoperability, which you can find on slideshare soon.
Please leave a comment.
Concept Maps are very effective for language-free expression and communication of concepts visually. The fundamental structures, which are not all graphic, are also very elegant for encoding knowledge for machine processing.
The building blocks of knowledge (Nodes and Links) are NOT sufficiently "expressive & precise". HyperPlex fills this need. See the PPT by that name in https://www.slideshare.net/putchavn
Both the concepts are explained with examples.
Good for general use and a prerequisite for knowing what is knowledge and how to represent it. Leave a comment.
[1] A view that a UseCase (UC) is a "dialog" between the System under Consideration (SuC) and an Actor (for a specific UC) brings focus to what "messages need to be exchanged between the SuC and Actor to reach UC Goal".
[2] Agreeing on and specifying UC Goal is related to business or application. UC Goal would be the right first step of UC description.
[3] There are many "means" of generating "messages from SuC", through various internal activities within the SuC. They need not be (I would even say should not be) specified in UC Description.
[4] The concept of UseCase is profound and useful because it is a "dialog" but NOT a process. This distinction is not defined and clarified which is why, I think, the full benefits of UC modeling are not widely realized.
[5] This view of UC (as per 1, 2 & 3) clearly separates the "internal processes" of the SuC from UC. The "internal processes" can be hypothesized and evolved separately using UML Sequence Diagrams. All the business / user needs can be specified with sufficient precision and rigor through the “messages” of UC dialog. There are no external dependencies, though constraints may exist and have to be taken care of.
I have REVISED & uploaded the PPT with TWO Sections, Section 2 First.
[6] I would like to study applications and demonstrate how the "dialog" view of UseCase would simplify & clarify UseCase description for the business user as well as system developer without sacrificing precision and usefulness.
02 FEB 14
Returning part of output back to input is considered feedback but this is NOT valid in all cases. This identifies what is missing in a complete FEEDBACK model: The User or Customer of the output. The feedback must come from the User of the output based on using the output. What such user gives is TRUE feedback. Many cases in which feedback works effectively it is because the feedback is TRUE. Such cases are discussed to support this view.
Use this and let me know your cases and how you are using TRUE feedback.
BA and RE Coaching, Training, Teaching,through Quizzes, Assignments, Mini Projects. Learning by DOING with MINIMUM LECTURING
Short intense Single Module Courses....of 4 to 6 Sessions.
The document discusses process modeling and identifies six key elements of a comprehensive process representation: 1) inputs, 2) activities performed by a performer, 3) outputs, 4) process resources and consumables, 5) undesirable inputs and outputs, and 6) feedback in and out. It argues that effective process modeling requires representing all six elements, including distinguishing between physical and logical flows, performers, and incorporating feedback loops. The six element model provides a complete way to analyze, communicate, and design processes.
CONTEXT of Context of the System(s) to be DevelopedPutcha Narasimham
Context Diagram or Use Case Diagram are created directly without many principles or guidelines for the validity of them. Many implicit assumptions and informal designs come into play. There is a need for the CONTEXT of context. It is here pointed out that Explicit TO BE Process is very helpful to overcome the limitations to prepare and assure that CD or UCD is valid and reliable. Three examples are added in this revision. An 8 Process example is used to show the method. See how it helps. Let's discuss.
These are TQM Quality Improvements Methods and Tools adapted for BA and RE. They are simple but potent if used with deep understanding and commitment.
All the tools are not discussed. End-Means Tree is excellent for planning and innovation.
I have added a PPT of 50 slides. It gives diagrams which I have not been able to add to text in this PDF.
See the PPT by the same name at www.slideshare.net/putchavn
What is normally called feedback may not be TRUE FEEDBACK. There are conditions to be applied. Only then can one realize the benefits of feedback. This understanding is necessary to design effective business processes that involve machines and humans.
This is an extended abstract for helping interaction. Feel free to email kenablersys@yahoo.com
Context
There are several commercial and open source drawing tools. Some of them are integrated into word processing and presentation tools. Some are very advanced and sophisticated drawing and picturing systems. However, none of them are as quick and convenient as sketching & writing on paper or whiteboard.
The Need
So, there is a need for a drawing tool that is fast, flexible and easy-to-use as sketching & writing and yet is capable of producing high quality diagrams.
Normally Use Case Diagrams are used but the pictorial information in it is so small that an MS Word Table is sufficient. What is more it can also provide space for "Use Case Goal" which is very important for Use Case Modeling.
Tables are quick and easy to create and edit. No need to waste time to draw and label diagrams. One can still do it if necessary after creating the Use Case TABLE. Try.
A Use Case Table can spill over into multiple pages but a diagram cannot!
UML 2.5 allows TABLES to be used for diagrams. So, there is no compulsion to create diagrams spending a lot of time.
Main Java[All of the Base Concepts}.docxadhitya5119
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
Philippine Edukasyong Pantahanan at Pangkabuhayan (EPP) CurriculumMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐄𝐏𝐏 𝐂𝐮𝐫𝐫𝐢𝐜𝐮𝐥𝐮𝐦 𝐢𝐧 𝐭𝐡𝐞 𝐏𝐡𝐢𝐥𝐢𝐩𝐩𝐢𝐧𝐞𝐬:
- Understand the goals and objectives of the Edukasyong Pantahanan at Pangkabuhayan (EPP) curriculum, recognizing its importance in fostering practical life skills and values among students. Students will also be able to identify the key components and subjects covered, such as agriculture, home economics, industrial arts, and information and communication technology.
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐍𝐚𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐚𝐧 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫:
-Define entrepreneurship, distinguishing it from general business activities by emphasizing its focus on innovation, risk-taking, and value creation. Students will describe the characteristics and traits of successful entrepreneurs, including their roles and responsibilities, and discuss the broader economic and social impacts of entrepreneurial activities on both local and global scales.
Temple of Asclepius in Thrace. Excavation resultsKrassimira Luka
The temple and the sanctuary around were dedicated to Asklepios Zmidrenus. This name has been known since 1875 when an inscription dedicated to him was discovered in Rome. The inscription is dated in 227 AD and was left by soldiers originating from the city of Philippopolis (modern Plovdiv).
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
2. What is a relation?
• Well known but difficult to define
• One ends up using association or connection
• They are just equivalent to relation
• But NOT definitions!
• Let’s look up online dictionary
• http://dictionary.reference.com/browse/relation?s=t
22JUL13Need to Redefine RELATION
2
Relation
What is it?
3. re·la·tion
• noun
• 1. an existing connection; a significant association
between or among things
• 2. connections in which persons or things are brought
together
• Well these are NOT precise and rigorous enough
• But one can get an idea of what a relation is
• Let’s see Math definition
22JUL13Need to Redefine RELATION
3
How is rain
related to clouds?
4. Relation—Math definition
A relation is any subset
of a Cartesian product
Consider two sets A & B
Then, relation is a subset
of CP of A&B
22JUL13Need to Redefine RELATION
4
Relation:
Subset of CP
of A & B
Set A
Men
Set B
Women
5. Cartesian Product Definition
• Cartesian Product of two sets A & B
• Is a set of all ordered pairs <a,b>,
• Where
• ‘a’ is an element of A &
• ‘b’ is an element of B
22JUL13Need to Redefine RELATION
5
Set A
Men
Set B
Women
6. Cartesian Product Explanation
• Every member of A
• is paired with
• every member of B
• To generate CP
• CP is the full set of all
possible pxq ordered
pairs
22JUL13Need to Redefine RELATION
6
Set A
Men
Set B
Women
M1
Mp
W1
W2
Wq
7. Relation: A subset of Cartesian Product
22JUL13Need to Redefine RELATION
7
Relation
Set A
Men
Set B
Women
M1, M2, M3, M4,
M5, M6, M7 … M20
W1, W2, W3, W4,
W5, W6, W7… W30
Subset
M2, W4
M4, W7
M5, W10
M9, W1
M13, W27
8. Ordered Pairs OK, but is it a relation?
1. We only see WHO are related
2. But don’t know
WHAT the relation is?
WHAT brings them into a relation?
And, HOW are they related?
22JUL13Need to Redefine RELATION
8
Subset
M2, W4
M4, W7
M5, W10
M9, W1
M13, W27
9. Is it a relation at all?
• It is just a set of ordered pairs
• WHAT is the basis to form pair?
• If any set is a relation, how is one
relation different from another, except
for the exact pairs?
• Is it not possible that the same pairs
are also related differently?
22JUL13Need to Redefine RELATION
9
Subset
M2, W4
M4, W7
M5, W10
M9, W1
M13, W27
10. Ordered Pairs & Relations
• Related Ordered Pairs
• Father and daughter,
• Brother and sister
• Husband and wife
• Mixed pairs for games
• Pairing alone is not relation
• Basis for pairing is relation
22JUL13Need to Redefine RELATION
10
Relation is
the basis for
pairing
NOT just
pairs
11. Arbitrary pairs remain unrelated
• One can form them but
what purpose do they
serve?
• What meaning or
significance do they
have?
• In businesses, societies and nature
there are always principles and
criteria guiding the formation of
classes (categories) and relations
• They are important
22JUL13Need to Redefine RELATION
11
12. Classes and Relations need basis
• This is the
motivation for
this proposal
22JUL13Need to Redefine RELATION
12
Classes and relations need a set
of principles and criteria for the
their formation as in OOAD, UML
They have identities and
properties for use and application
13. Relation is as fundamental as set
Is a member of is a relation
between an object and the set to
which it belongs
The concept of relation and set
perhaps emerge interdependently
and simultaneously
This may have been
sorted out in some
fundamental theories
of mathematics and or
philosophy
13
22JUL13Need to Redefine RELATION
14. Relation Redefined for clarity and use
• The mathematical definition of relation
appears unmathematical and leaves many
questions unanswered
• It is enumerative & unusable
• Runs into anomalies and paradoxes
• So, here is a proposed definition of relation
22JUL13Need to Redefine RELATION
14
15. Proposed Definition of relation
A relation between two sets A and
B is a named set of principles and
criteria, according to which
ordered pairs can be formed from
A and B.
Criteria for forming
ordered pairs are
more important
than the pairs
This resolves many
questions
See PDF--Relation:
Need for Radical
Redefinition
15
22JUL13Need to Redefine RELATION
16. How does this definition help?
• Now, we know what a relation is and how to
use it without forming ordered pairs first
• We know how relation applies for the FUTURE
members of sets involved
• We can use it to define, create, VERIFY and
apply relations correctly and infer from them
22JUL13Need to Redefine RELATION
16
17. Let’s THINK and Discuss
• A definition should be clear, consistent
and self-sufficient for application and
use.
• I believe the proposed definition is
• I welcome reviews, examples,
counter examples and feedback
22JUL13Need to Redefine RELATION
17
START
kenablersys@yahoo.com