Business Systems Books
Related Subjects: Document Imaging Enterprise Applications - ERP and ERM Accounting Document Management
More Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250

I concur with the above reviewReview Date: 2006-12-08
Why is one of my articles for sale on Amazon?Review Date: 2005-06-14
What the hell is my article doing on Amazon, and do I get any money from the sales of the article?
These are questions that will probably never be answered.

Used price: $0.47

Written by top finance professorsReview Date: 2000-08-08
Useful concise bookReview Date: 2000-12-10

Used price: $120.51

Field Applications EngineerReview Date: 2002-12-23
My knowledge needs to be as broad as possible. My expertise is limited in a very specific narrow area. I felt like a "handicapped" when I talk to my customers on the project details they work on. After reading Success By Learning, it gave me a better insight on hardware, firmware programming, Internet, Ethernet, networking. As a result, it helps me sell my products easier and I get more respect from my customers.
Success By learningReview Date: 2001-08-15

Used price: $25.69

InspiringReview Date: 2008-03-09
Many ideas for improving performanceReview Date: 2004-01-30
One chapter is devoted to Allen Sheppard and GrandMet where the goal was to take a successful company, ensure it continued to be successful, and make it even more successful. Often this situation is more difficult than a typical turnaround, because people do not see the need to change. The top group developed a set of criteria for a vision statement that was so far reaching that it could not be publicized for two years but it led to the sale of 25 companies and the acquisition of Pillsbury. Another chapter presents the remarkable success story of Toray Industries and the role visioning played in its transformation in the decade from 1987. Describing the way in which vision works, H. Maeda said, "We keep the image in our minds at all times when we take decisions on various business matters. Keeping the picture of our company in say, ten year's time, we decide on management strategy and business policy. In a company of this size, the leadership of the president is absolutely crucial. He must be able to exercise his leadership at a fairly practical level, and have a management philosophy as well as an ability to manage. Another important quality he needs is the ability to win the hearts and minds of all employees and to inspire them to focus on the shared goal. I believe that a CEO must be prepared to hear everyone's views, let them discuss thoroughly matters that are important to management, and get totally involved in the process of building up consensus among directors. This will ensure that the future direction of the firm will become firmly established on shared values, but the important point is that there must be constant effort on the CEO's part to create and maintain a forum at which all directors can express their views freely to the CEO. There are many facets to leadership, but to put it simply, it is the ability of the leaders to anticipate what is coming, and the possession of the sense of balance in their judgement." Few people will read this book and not come away with ideas for improvement.

Used price: $19.51

Just do it!Review Date: 2008-03-01
Good read review from CashFlow QueenReview Date: 2008-01-15

Used price: $45.96

Fantastic reading for anyone in a leadership position. Review Date: 2007-11-06
A must have for any company, big or small. Review Date: 2007-09-21

Used price: $3.03

Reinventing Strategic PlanningReview Date: 2007-09-29
Define your Ideal Future Vision and desired outcomes within the context of the Future Environment at the future year of your Vision is how to begin. Then, Haines has you use "Backwards Thinking" to today to be able to close the gap from today to the future. The problem with most planning that starts with today as there is no gap to close to take you to the future because you have not defined your desired outcomes first.
Shows how systems thinking accommodates multi-level change.Review Date: 1999-06-13
The book outlines systems thinking clearly, and shows how it can be applied to virtually any multi-level change.
Haines makes managers see how the natural laws of his systems thinking approach can easily fit their planning models for viable strategies and desired solutions within the complexities of a new millenium.

Used price: $25.00

Recommended for students of contemporary Russian societyReview Date: 2001-03-19
Recommended for students of contemporary Russian societyReview Date: 2001-03-19


Key to successful integration projects & CMMIReview Date: 2001-02-22
It starts with a foundation of the basics, such as definitions, system engineering life cycle, analysis and concurrent engineering. It then builds upon this foundation by addressing all of the elements of a well-managed system engineering program: integrated product and process development, TQM, configuration management, support and logistics. Each element is discussed in detail and placed into the context of a total system engineering environment.
The chapter on system design requirements is particularly complete and covers every facet of this discipline, including reliability, maintainability, safety, software, etc. There is a lot of good material here, which is reinforced by the next chapter that covers design tools and methods. The design process is concluded by a chapter on design review and evaluation, which is a foundation of good quality practices as well as a well-written SEMP.
The real heart of the book starts in chapter 6, which covers SE program planing. It covers program requirements, the SEMP itself and provides a statement of work. It then provides a complete work breakdown structure for implementing system engineering functions and tasks. This chapter provides a risk management plan that is well thought out and serves as an excellent template. It also addresses the CMM for systems engineering. Much of this material has been superseded by the Software Engineering Institute's CMMI that now covers system engineering, software engineering and integrated product and process development. This is not a problem because the book's coverage of the CMM-SE is consistent with the material in the CMMI.
The final two chapters, addressing system engineering organization and supplier/sub contractor management are to the point and contains a lot of valuable information.
Had the author provided this book in soft copy on an accompanying diskette or CD ROM it would be a best seller on the Beltway because of the time it would save in developing a company-wide system engineering procedure manual.
Consulting companies and IT departments would also greatly benefit from this book because of the structured approach it provides for planning and managing system integration. Unlike their cousins in the government contracting and CMM domains, they generally approach system engineering and integration in a loose fashion that too often results in cost and schedule overruns, or project cancellation. By following the approach outlined in this book consulting companies and IT departments would find that technical, cost and schedule risks would be identified early and controlled, and that the design, integration and implementation of complex systems would enjoy a higher rate of success. This is especially true when multiple vendors are involved in an integration project - the material in chapters 1 (integrated process teams) and 8 (subcontractor management) provides a foundation for managing cross-functional teams. Therefore, I strongly recommend this book for engagement and project managers, and program management offices run by consulting companies and/or IT departments.
Excellent Introduction to Systems Engineering Review Date: 2005-12-17
Systems engineering is essentially the function that oversees any design effort to ensure that the resulting design does what it's supposed to. As such requirements are the bread and butter of systems engineering. The most visible job of the system engineer then is to turn the customer's desires into functional requirements, and then turn those requirements into something that can be designed to based on the system architecture the designers / system engineers prefer.
For example, consider if you have a city with a river through it and the local government wants to develop a system to carry cars across the river. The system engineer would first turn that desire into functional requirements. These would include requirements like: No. of cars per hour that can transit, can't interfere with riverborne ship traffic, growth in traffic that can be absorbed etc. From this you have something that you can verify design concepts against to see if they satisfy the customer desires, but actually can't pull out the ruler and calculators just yet. Systems engineers / designers would then consider options like a suspension bridge, a ferry system, or a tunnel beneath the river. Each of these system options would have their own architectures and the functional requirements would have to be translated into different design requirements for each. The bridge would have to be so high to allow ship traffic and have so many lanes and bear so much live weight. The ferry system would need so many ferries of such and such a carrying capacity. The tunnel would have to have so many lanes, would require such and such a ventilation capacity, etc. The systems engineer would be involved in determining which of these architectures would best suit customer needs, and then turn the functional requirements into the design to requirements so design work can begin in earnest.
Of course as design work continues and large components are broken down into smaller and smaller design components the systems engineer continues to guide the choice of how to configure the lower tier of design components, and to allocate design to requirements for them. If the system engineer has done their job right when all the design components are integrated into each other the resulting system really does what it was intended to do and meets the functional requirements.
This book tells you in a very clear, completely comprehensive, and extremely well laid out manner how to do this. It also tells you why you should do this, and how it is beneficial. The writing is straightforward, always to the point, and easily understood. The topic is pertinent and can help you understand how systems are actually engineered in the real world, a very rare and very appreciated breath of fresh air in engineering textbooks.
The author also covers all the aspects of systems engineering planning, including scheduling, budgeting, contracting, and system verification / validation, etc. Systems engineering is largely a management function so this information is interesting and necessary for the subject.
This book will be extremely helpful for engineers of any stripe who want to put their work into context, systems engineers for how to do what their supposed to do, and for contractors and government purchasers to implement processes to guarantee that they get a system that does what they want. (Provided what they want is feasible of course!)
Certainly recommended and a book that I use frequently for reference.

Used price: $12.99

Something rare: a new ideaReview Date: 2003-01-23
Actually, there are several new ideas. One them is that professions restrict their markets when they attempt to raise their fees by adding barriers to entry. Since demand is stable or rising, this creates opportunity for other groups to move in "below." As physicians' time becomes ever more valuable, RNs achieve the status of practitioners and LPNs fill in. Aides are now certified, and so on. This seminal idea was published in 1988. Almost ten years later, Clayton Christensen described in his well-regarded Innovators' Dilemma how a corporate fixation on upselling existing customers assured that less lucrative markets would be neglected, providing rich opportunities for new entrants. The parallel is striking.
Whether you have any interest in his topic, Abbott's exposition is worth studying as a model of effective rhetoric. And the writing is vivid; he worked for years in a large mental hospital, "After five years, . . . I had helped administer several tons of thorazine, mellaril and their cousins . . ."
one of the best books in social scienceReview Date: 2004-04-04
In this book, Abbott argues that each profession is bound to a set of tasks by ties of jurisdiction, the strengths and weaknesses of these ties being established in the processes of actual professional work. The central thesis of the book is that the professions make up an interdependent system, in which each profession has its activities under various kinds of jurisdiction. Jurisdictional boundaries are perpetually in dispute. Professions develop through competitions for jurisdictions over work.
Abbott's focus on professional work and interaction is clearly an ecological perspective along the line of the famous Chicago tradition in sociology. If you are interested in knowing more about this tradition, another book by the same author - Department and Discipline - would be a good place to start from.
As I said, you could not finish the book in one night without missing some really fascinating stuff. You'd probably also be amazed by the incredible coherence in Abbott's theory. For the sociology of professions, this book is both revolutionary and devastating - the field has been dead for more than 15 years since it was published in 1988!
Related Subjects: Document Imaging Enterprise Applications - ERP and ERM Accounting Document Management
More Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250