Modeling an enterprise

Many reasons why, 1) to preserve knowledge 2) identify teams that help the

enterprise achieve it's goals 3) compliance requirements 4) dates and more

Vensim: a soft system Diagram

Ventana Systems, Inc. provides products and services to solve hard problems and improve organizational performance. Ventana publishes Vensim which is used for constructing models of business, scientific, environmental, and social systems.

This is an excellent tool that I learned for my Systems 710 class. It's in some way a brainstorming tool that would eventually organize your thoughts. It also links individual states to each other, to show a positive or negative association to one another.

I'm planning to use this to depict the obstacles to earning my PhD at Stevens with this tool. I'm sure the outcome will be beneficial, one way or another.

Heterogeneity

Heterogeneous is an adjective used to describe an object or system consisting of multiple items having a large number of structural variations. It is the opposite of homogeneous, which means that an object or system consists of multiple identical items.

In the world of enterprise computing, heterogeneous data is a mix of data from two or more sources, often of two or more formats, e.g., SQL and XML. Distributed systems are called heterogeneous if they contain many different types of hardware and software. heterogeneity of the system means the ability of that system to work with different systems

 

A champion in Systems Engineering

Lecturers and Instructors have the important responcibility of educating others. There are poeple who do the work, and there are others who DO IT RIGHT. Eirik Hole, a lecturer at Stevens Inst of Technology, is a well spoken and detail oriented individual with a sharp eye for Systems.

He has the knowledge and capability to instruct a diverse class, and brings excitement and enthusiasm to the class environment. Given the criticality of Systems Engineering in the next decade, it is vital to keep up with todays current events, and prepare for a System Oriented mindset of tomorrow.

Money/Payscale's Best Jobs Survey

From CNN Money:
#1 Job: Systems Engineering!!!!!!
What they do: They're the "big think" managers on large, complex projects, from major transportation networks to military defense programs. They figure out the technical specifications required and coordinate the efforts of lower-level engineers working on specific aspects of the project.

Why it's great: Demand is soaring for systems engineers, as what was once a niche job in the aerospace and defense industries becomes commonplace among a diverse and expanding universe of employers, from medical device makers to corporations like Xerox and BMW.

Pay can easily hit six figures for top performers, and there's ample opportunity for advancement. But many systems engineers say they most enjoy the creative aspects of the job and seeing projects come to life. "The transit system I work on really makes a tangible difference to people," says Anne O'Neil, chief systems engineer for the New York City Transit Authority.

http://money.cnn.com/magazines/moneymag/bestjobs/2009/snapshots/1.html

Systems thinking and keywords in the area

According to managementhelp.org, systems thinking is a way of helping a person to view systems from a broad perspective that includes seeing overall structures, patterns and cycles in systems, rather than seeing only specific events in the system. This broad view can help you to quickly identify the real causes of issues in organizations and know just where to work to address them. Systems thinking has produced a variety of principles and tools for analyzing and changing systems.

By focusing on the entire system, consultants can attempt to identify solutions that address as many problems as possible in the system. The positive effect of those solutions leverages improvement throughout the system. Thus, they are called “leverage points” in the system. This priority on the entire system and its leverage points is called whole systems thinking.

Also look at :http://www.pegasuscom.com/systems-thinking.html

Keywords: Links, Scopes, Principles of Change,Causal Loop Diagrams, Systems Diagrams, Five Disciplines of Systems Thinking,Chaos Theory

History of Use Cases

A use case in software engineering and systems engineering is a description of a system’s behavior as it responds to a request that originates from outside of that system. In other words, a use case describes "who" can do "what" with the system in question. The use case technique is used to capture a system's behavioral requirements by detailing scenario-driven threads through the functional requirements.

In 1986, Ivar Jacobson, later an important contributor to both the Unified Modeling Language (UML) and the Rational Unified Process (RUP), first formulated the visual modeling technique for specifying use cases. Originally he used the terms usage scenarios and usage case, but found that neither of these terms sounded natural in English, and eventually he settled on the term use case. During the 1990s use cases became one of the most common practices for capturing functional requirements. This is especially the case within the object-oriented community where they originated, but their applicability is not restricted to object-oriented systems, because use cases are not object-oriented in nature.

Project Management: Solar Tower

An example of excellent project Management in my opinion. I will post more about this in the near future, as I am doing an extensive case study on the Seville Solar Power. This is an awesome project that deserves way more attention as it has been getting. So I'm going to contribute to the body of works that has been published out there.

A great Systems Software

Hello and Welcome

Hello,
Thank you for checking out this blog. It is my intent to share interesting discussions that relate to the world of Systems.

Please bookmark and check these pages often.

Yours,
Matin Sarfaraz