Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
I'm developing a preventive maintenance strategy for an industrial plant based on RCM (Reliability Centered Maintenance) methodology. For this job, I need to choose one CMMS (Computerized maintenance management system) among several options but I need to do it in a clever way.
Is there some technical procedure to make a Comparative Assessment of Software Programs and get to know what is the better CMMS option? Any standard, table or matrix?
Thank you so much
I found an insteresting document with a Comparative Assessment of Software
Programs very useful for me developed by the IRIS Center at the University of Maryland.
Comparative Assessment of Software
Programs for the Development of
Computer-Assisted Personal Interview
(CAPI) Applications
This scientific article could be useful as well:
Comparative Assessment of Software Quality Classification Techniques: An Empirical Case Study
EDIT
There are Sites like Quora that are better places to make this kind of questions
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
I am new to software engineering and also I like to learn whatever new. I must be very thankful if someone help me to provide further information about How is a UI evaluated?.
Any help regarding to this matter is highly appreciated.
In common, evaluation of User Interface can be based on three common elements
• Functionality
• Aesthetics
• Performance
Functionality
Is the application usable?
Does it enable users to complete tasks?
Aesthetics
Style
How it influencing the users
How shown and presented?
How colors complement each other?
How UI elements convey their meaning?
Performance
Measured not only by speed, but also reliability.
Reliability (Even though an application looks good and feels great, crashes repeatedly, it likely won’t be very successful)
Should provide a user with full confidence.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
For the past 3 semesters at school I've been taking software engineering classes where we've been learning about the various life-cycle models. The textbook for the course is a collection of IEEE articles from the 1970s and 1980s. The professors has a generally negative attitude towards just about every model. He says they are all useless. The main models we talk about are waterfall, evolutionary, incremental, spiral, and my favorite (sarcasm), the automated software synthesis model.
My questions:
What are some other models used today (even if only in theory, as in the case of automatic software synthesis)?
and
What is the most prevalent model used for large projects in the industry (Google, Microsoft, Apple, etc.)?
I hear a lot of people talk about using Agile, but more often than not I get the impression that they're not really talking about an actual life-cycle model. I think most of the time people just mean that they don't design or document like they should...
See this questions on programmers (which was closed, but still an excellent reference starting point): Are there any major alternatives to waterfall and Agile?
Nearly all of these lifecycle models have been used successfully in industry on large projects, some more easily than others. Choice of lifecycle model depends on many factors including size, cost, safety concerns, time, volatility, "researchiness" of the project, risk, stakeholders, schedule needs, etc and may vary from project to project, even within the same company.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
What do these mysterious "Business Intelligence" software do anyway ?
They're not really mysterious. BI or Business Intelligence software is just a term that groups software with a particular goal like OLAP and report generators. SSRS and Crystal Reports are some examples, among many others.
And the requisite wiki article...
In a nutshell, the goal of BI is: aggregating and presenting data to help executive decision making.
In a business, the role of a CEO is to stay on top of pretty much everything that is happening in a company. Some data you can get off of standardized reports, but sometimes you have an intuition, and need to actually dig through the data in arbitrary ways, while not really being able to learn SQL. BI is there to fill that role. It is there to do a better job then the CEO actually exporting a bunch of reports into excel, then massaging the data there.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm interested to know if there is any literature out there on the relationship of complexity theory (emergence, complex systems, evolution) and software development processes. I read somewhere that SCRUM philosophy came out of the theory of punctuated equilibrium in evolution theory. Are there any additional studies/researches on this subject?
Thanks!
There's a slightly tongue-in-cheek book called Systemantics. Because a software program is a type of system, its observations are applicable to software: for example,
The bigger the system, the narrower and more specialized the interface with individuals.
A complex system cannot be "made" to work. It either works or it doesn't.
A simple system, designed from scratch, sometimes works.
Some complex systems actually work.
A complex system that works is invariably found to have evolved from a simple system that works.
A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over, beginning with a working simple system.
There interesting blog posts by Jurgen Appelo of NOOP.NL fame, which are related to application of complexity theory to software engineering and project management:
Your Project Will Suffer From Power Laws
What (Else) Can Agile Learn from Complexity?
These can be helpful in researching this topic.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Someone within my organization has started pushing for us to pilot the CMU SEI's TSP process (see website here). I have an instinctual aversion to any attempts to cure software development illnesses with alphabet soup, but I would like to know if anyone has experience with this process and can provide tangible facts.
I used to be a fan of SEI's CMM. I even read Watts Humphrey's "Managing the Software Process" book cover to cover. I haven't used TSP but I suspect it has similar strenghts and weaknesses as the other software processes.
Definitely read about it and what they claim it can do and how to implement it, but be vigilant about keeping your software process small and flexible. You need one, but be careful about taking processes from someone else.
good luck.
We've been using this process for a few months now and I'm not particularly impressed. This process is only suitable for a strict command and control style of management where programmers are essentially bean counters. Most of the good parts of this process (size estimates rather than time estimates, self reviews, detailed plans, logging time against plans, and keeping a log of defects and errors for later review) can be implemented without throwing a bunch of money at SEI.