Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #14568

More of my philosophy about the Post Graduate Program on lean Six Sigma and more..

Show all headers | View raw

Hello,


More of my philosophy about the Post Graduate Program on lean Six Sigma and more..

I am a white arab, and i think i am smart since i have also
invented many scalable algorithms and algorithms..


More of my philosophy about Six Sigma and more..

I think i am smart, and now i will talk more about Six Sigma
since i have just talked about SPC(Statistical quality control), so
you have to know that Six Sigma needs to fulfill the following steps:

1- Define the project goals and customer (external and internal)
   deliverables.

2- Control future performance so improved process doesn't degrade.

3- Measure the process so that to determine current performance and
   quantify the problem.

4- Analyze and determine the root cause(s) of the defects.

5- Improve the process by eliminating the defects.


And you have to know that those steps are also important steps toward attaining ISO 9000 certification, and notice that you can use SPC(Statistical process control) and the control charts on step [4] and step [5] above.

Other than that i have just read the following interesting important paper about SPC(Statistical process control) that explains all the process of SPC(Statistical process control), so i invite you to read it
carefully:

https://owic.oregonstate.edu/sites/default/files/pubs/EM8733.pdf

So as you notice in the above paper that the central limit theorem
in mathematics is so important, but notice carefully that the necessary and important condition so that the central limit theorem works is that you have to use independent and random variables, and notice in the above paper that you have to do two things and it's that you have to reduce or eliminate the defects and you have to control the "variability" of the defects, and this is why the paper is talking about how to construct a control chart. Other than that the central limit theorem is not only related to SPC(Statistical process control), but it is also related to PERT and my PERT++ software project below, and notice that in my software project below that is called PERT++, i have provided you with two ways of how to estimate the critical path, first, by the way of CPM(Critical Path Method) that shows all the arcs of the estimate of the critical path, and the second way is by the way of the central limit theorem by using the inverse normal distribution function, and you have to provide my software project that is called PERT++ with three types of estimates that are the following:

Optimistic time - generally the shortest time in which the activity
can be completed. It is common practice to specify optimistic times
to be three standard deviations from the mean so that there is
approximately a 1% chance that the activity will be completed within
the optimistic time.

Most likely time - the completion time having the highest
probability. Note that this time is different from the expected time.

Pessimistic time - the longest time that an activity might require. Three standard deviations from the mean is commonly used for the pessimistic time.

And you can download my PERT++ from reading my following below thoughts:

More of my philosophy about the central limit theorem and about my PERT++ and more..

The central limit theorem states that the sampling distribution of the mean of any independent, random variable will be normal or nearly normal, if the sample size is large enough.

How large is "large enough"?

In practice, some statisticians say that a sample size of 30 is large enough when the population distribution is roughly bell-shaped. Others recommend a sample size of at least 40. But if the original population is distinctly not normal (e.g., is badly skewed, has multiple peaks, and/or has outliers), researchers like the sample size to be even larger. So i invite you to read my following thoughts about my software
project that is called PERT++, and notice that the PERT networks are referred to by some researchers as "probabilistic activity networks" (PAN) because the duration of some or all of the arcs are independent random variables with known probability distribution functions, and have finite ranges. So PERT uses the central limit theorem (CLT) to find the expected project duration.

And as you are noticing this Central Limit Theorem is also so important
for quality control, read the following to notice it(I also understood Statistical Process Control (SPC)):

An Introduction to Statistical Process Control (SPC)

https://www.engineering.com/AdvancedManufacturing/ArticleID/19494/An-Introduction-to-Statistical-Process-Control-SPC.aspx

Also PERT networks are referred to by some researchers as "probabilistic activity networks" (PAN) because the duration of some or all of the arcs are independent random variables with known probability distribution functions, and have finite ranges. So PERT uses the central limit theorem (CLT) to find the expected project duration.

So, i have designed and implemented my PERT++ that that is important for quality, please read about it and download it from my website here:

https://sites.google.com/site/scalable68/pert-an-enhanced-edition-of-the-program-or-project-evaluation-and-review-technique-that-includes-statistical-pert-in-delphi-and-freepascal

---


So I have provided you in my PERT++ with the following functions:


function NormalDistA (const Mean, StdDev, AVal, BVal: Extended): Single;

function NormalDistP (const Mean, StdDev, AVal: Extended): Single;

function InvNormalDist(const Mean, StdDev, PVal: Extended; const Less: Boolean): Extended;

For NormalDistA() or NormalDistP(), you pass the best estimate of completion time to Mean, and you pass the critical path standard deviation to StdDev, and you will get the probability of the value Aval or the probability between the values of Aval and Bval.

For InvNormalDist(), you pass the best estimate of completion time to Mean, and you pass the critical path standard deviation to StdDev, and you will get the length of the critical path of the probability PVal, and when Less is TRUE, you will obtain a cumulative distribution.


So as you are noticing from my above thoughts that since PERT networks are referred to by some researchers as "probabilistic activity networks" (PAN) because the duration of some or all of the arcs are independent random variables with known probability distribution functions, and have finite ranges. So PERT uses the central limit theorem (CLT) to find the expected project duration. So then you have to use my above functions
that are Normal distribution and inverse normal distribution functions, please look at my demo inside my zip file to understand better how i am doing it:

You can download and read about my PERT++ from my website here:

https://sites.google.com/site/scalable68/pert-an-enhanced-edition-of-the-program-or-project-evaluation-and-review-technique-that-includes-statistical-pert-in-delphi-and-freepascal

I think i am smart and i invite you to read carefully the following webpage of Alan Robinson Professor of Operations Management at University of Massachusetts and that is a full-time professor at the Isenberg School of Management of UMass and a consultant and book author specializing in managing ideas (idea-generation and idea-driven organization) and building high-performance organizations, creativity, innovation, quality, and lean management:

https://www.simplilearn.com/pgp-lean-six-sigma-certification-training-course?utm_source=google&utm_medium=cpc&utm_term=&utm_content=11174393172-108220153863-506962883161&utm_device=c&utm_campaign=Display-MQL-DigitalOperationsCluster-PG-QM-CLSS-UMass-YTVideoInstreamCustomIntent-US-Main-AllDevice-adgroup-QM-Desktop-CI&gclid=Cj0KCQiA3rKQBhCNARIsACUEW_ZGLHcUP2htLdQo46zP6Eo2-vX0MQYvc-o6GQP55638Up4tex85RBEaArn9EALw_wcB


And notice in the above webpage of the professor, that he is giving Post Graduate Program in Lean Six Sigma and on agile methodology, and i think that this Post Graduate Program is easy for me since i am really smart and i can easily understand lean Six Sigma or Six Sigma and i can easily understand agile methodology, and notice that i am in my below thoughts also explaining much more smartly what is agile methodology, and i think that the more difficult part of Six Sigma or lean Six Sigma is to understand the central limit theorem and to understand what is SPC(Statistical quality control) and how to use the control charts so that to control the variability of the defects, and notice that i am talking about it in my below thoughts, but i think that the rest of lean Six Sigma and Six Sigma is easy for me.


More of my philosophy about trust and about evolutionary algorithms and more..

I think i am smart and i say that even Evolutionary Design methodology or evolutionary algorithms have to be based on "trust", i mean that look at how we have to ensure the global convergence of the evolutionary algorithm, so this kind of trust is like scientific, and notice that we are using in Evolutionary Design methodology the Unit Testing, Test Driven Development, Design Patterns, Continuous Integration, Domain Driven Design, and we have to grow "nicely" and "balanced" the complex software projects by using standards, and we have to optimize growth of the complex software projects by balancing between the criteria of the easy to change the complex software projects and the performance of the complex software projects, and we have to maximize the growth of the complex software projects by making the most out of each optimization, so as you notice that even Evolutionary Design methodology is based on trust and it is like scientific since read my following proverb about trust so that you notice:

"There is an important difference between the appearance of a reality
and the truth of a reality, this is why in science you have not to be
confident with the appearances, since in science you have to understand
the truth, so, to be able to understand the truth you have to know how
to be patience before understanding the truth and not to rush in like a
fool by lack of wisdom "

And i invite you to read my following thoughts about evolutionary algorithms and artificial intelligence so that to understand more:

https://groups.google.com/g/alt.culture.morocco/c/P9OTDTiCZ44

And read my following thoughts about Evolutionary Design methodology that is also based on "trust" and that is so important so that to understand:

And I invite you to look at step 4 of my below thoughts of software Evolutionary Design methodology with agile, here it is:

4- When in agile a team breaks a project into phases, it’s called
   incremental development. An incremental process is one in which
   software is built and delivered in pieces. Each piece, or increment,
   represents a complete subset of functionality. The increment may be
   either small or large, perhaps ranging from just a system’s login
   screen on the small end to a highly flexible set of data management
   screens. Each increment is fully coded Sprints, Planning, and
   Retrospectives.

And you will notice that it has to be done by "prioritizing" the pieces of the software to be delivered to the customers, and here again in agile you are noticing that we are also delivering prototypes of the software, since we often associate prototypes with nearly completed or just-before launch versions of products. However, designers create prototypes at all phases of the design process at various resolutions. In engineering, students are taught to and practitioners think deeply before setting out to build. However, as the product or system becomes increasingly complex, it becomes increasingly difficult to consider all factors while designing. Facing this reality, designers are no longer just "thinking to build" but also "building to think." By getting hands on and trying to create prototypes, unforeseen issues are highlighted early, saving costs related with late stage design changes. This rapid iterative cycle of thinking and building is what allows designers to learn rapidly from doing. Creating interfaces often benefit from the "build to think" approach. For example, in trying to layout the automotive cockpit, one can simply list all the features, buttons, and knobs that must be incorporated. However, by prototyping the cabin does one really start to think about how the layout should be to the driver in order to avoid confusion while maximizing comfort. This then allows the designer iterate on their initial concept to develop something that is more intuitive and refined. Also prototypes and there demonstrations are designed to get potential customers interested and excited.

More of my philosophy about the Evolutionary Design methodology and more..

Here are some important steps of software Evolutionary Design methodology:

1- Taking a little extra time during the project to write solid code and
   fix problems today, they create a codebase that’s easy to maintain
   tomorrow.

2- And the most destructive thing you can do to your project is to build
   new code, and then build more code that depends on it, and then still
   more code that depends on that, leading to that painfully familiar
   domino effect of cascading changes...and eventually leaving you with
   an unmaintainable mess of spaghetti code. So when teams write code,
   they can keep their software designs simple by creating software
   designs based on small, self-contained units (like classes, modules,
   services, etc.) that do only one thing; this helps avoid the domino
   effect.

3- Instead of creating one big design at the beginning of the project
   that covers all of the requirements, agile architects use incremental
   design, which involves techniques that allow them to design a system
   that is not just complete, but also easy for the team to modify as
   the project changes.

4- When in agile a team breaks a project into phases, it’s called
   incremental development. An incremental process is one in which
   software is built and delivered in pieces. Each piece, or increment,
   represents a complete subset of functionality. The increment may be
   either small or large, perhaps ranging from just a system’s login
   screen on the small end to a highly flexible set of data management
   screens. Each increment is fully coded Sprints, Planning, and
   Retrospectives.

5- And an iterative process in agile is one that makes progress through
   successive refinement. A development team takes a first cut
   at a system, knowing it is incomplete or weak in some (perhaps many)
   areas. They then iteratively refine those areas until the product is
   satisfactory. With each iteration the software is improved through
   the addition of greater detail.

More of philosophy about Democracy and the Evolutionary Design methodology..

I will make a logical analogy between software projects and Democracy,
first i will say that because of the today big complexity of software
projects, so the "requirements" of those complex software projects are
not clear and a lot could change in them, so this is
why we are using an Evolutionary Design methodology with different tools
such as Unit Testing, Test Driven Development, Design Patterns,
Continuous Integration, Domain Driven Design, but we have to notice
carefully that an important thing in Evolutionary Design methodology is
that when those complex software projects grow, we have first to
normalize there growth by ensuring that the complex software projects
grow "nicely" and "balanced" by using standards, and second we have to
optimize growth of the complex software projects by balancing between
the criteria of the easy to change the complex software projects and the
performance of the complex software projects, and third you have to
maximize the growth of the complex software projects by making the most
out of each optimization, and i think that by logical analogy we can
notice that in Democracy we have also to normalize the growth by not
allowing "extremism" or extremist ideologies that hurt Democracy, and we
have also to optimize Democracy by for example well balancing between
"performance" of the society and in the Democracy and the "reliability"
of helping others like the weakest members of the society among the
people that of course respect the laws, and so that to understand more
my thoughts of my philosophy about Democracy, i invite you to read them
here:

https://groups.google.com/g/alt.culture.morocco/c/vlDWhmf-MIM


Thank you,
Amine Moulay Ramdane.

Back to comp.programming | Previous | Next | Find similar | Unroll thread

Thread

More of my philosophy about the Post Graduate Program on lean Six Sigma and more.. Amine Moulay Ramdane <aminer68@gmail.com> - 2022-02-18 13:07 -0800

csiph-web