Aamdani Atthanni Kharcha Rupaiya (2001)

Star: Govinda ... Bhimsha Juhi Chawla ... Jhoomri Tabu ... Meena Chandrachur Singh ... Ravi Johnny Lever ... Appu Khote .........

Mehndi (1998)

Star: Faraaz Khan ... Niranjan Chaudhary Rani Mukherjee ... Pooja (as Rani Mukherji) Ushma Rathod Shakti Kapoor ... Banne Miya Arjun ... Billoo Joginder Shelly ... Police Inspector Bhisham (as Joginder)

Money Train (1995) (In Hindi)

Star: Wesley Snipes ... John Woody Harrelson ... Charlie Jennifer Lopez ... Grace Santiago Robert Blake ... Donald Patterson Chris Cooper ... Torch Joe Grifasi ... Riley Scott Sowers ... Mr. Brown Skipp Sudduth ... Kowalski

You've Got Mail (1998) (In Hindi)

Star: Tom Hanks ... Joe Fox Meg Ryan ... Kathleen Kelly Katie Sagona ... Young Kathleen Kelly Greg Kinnear ... Frank Navasky Parker Posey ... Patricia Eden Jean Stapleton ... Birdie Conrad Steve Zahn ... George Pappas Heather Burns ... Christina Plutzker

Mazaaq (1975)

Posted by 1213 On 10:43 PM

Star: Vinod Mehra ... Vinod Moushumi Chatterjee ... Moushumi Mehmood ... Raja Aruna Irani ... Dr. A. Irani Iftekhar ... Moushumi's Father Bhagwan G. Asrani ... Murali / Marlon Kanhaiyalal ... Murali's Father Agha ... Gaylord Hotel Manager

Showing posts with label software engineering. Show all posts
Showing posts with label software engineering. Show all posts







Book Details

•Paperback: 432 pages
•Publisher: Apress; 1 edition (August 5, 2003)
•Language: English
•ISBN-10: 1590590961
•ISBN-13: 978-1590590966

Book Description

…from my experience, most teams that say they’re doing XP don’t actually do the practices.

— Alistair Cockburn, Xp And The Cmm

Extreme Programming Refactored: The Case Against XP (featuring Songs of the Extremos) takes a satirical look at the increasingly hyped Extreme Programming methodology. It explores some quite astonishing Extremo quotes that have typified the XP approach quotes such as, “XPers are not afraid of oral documentation,” “Schedule is the customers problem,” “Dependencies between requirements are more a matter of fear than reality” and “Concentration is the Enemy.”

In between the chuckles, though, there is a serious analysis of XPs many flaws. The authors also examine C3, the first XP project, whose team (most of whom went on to get XP book deals shortly before C3s cancellation) described themselves as “the best team on the face of the Earth”. (In a later chapter, the authors also note that one problem which can affect pair programmers is overconfidence or is that “eXcessive courage”?). The authors examine whether the problems that led to C3s “inexplicable” cancellation could also afflict present-day XP projects.

In the final chapter (Refactoring XP) Matt and Doug suggest some ways of achieving the agile goals of XP using some XP practices (used in moderation) combined with other, less risk-laden methods.


--------------------------------------------------------------------------------
This just in from Slashdot.org: Take 2, six months later and still going strong!

See what reviewers at Slashdot.org originally had to say about Matt and Doug’s book!



--------------------------------------------------------------------------------

Download Description
“Any one [XP] practice doesn’t stand well on its own (with the possible exception of testing). They require the other practices to keep them in balance.” – Kent Beck, Extreme Programming Explained, (Chapter 11)

“Well, from my experience, most teams that say they’re doing XP don’t actually do the practices.

“Houston, we have a problem.” – Jim Lovell, Apollo 13

Extreme Programming Refactored: The Case Against XP (featuring Songs of the Extremos) takes a satirical look at the increasingly hyped Extreme Programming methodology. It explores some quite astonishing Extremo quotes that have typified the XP approach— quotes such as, “XPers are not afraid of oral documentation,” “Schedule is the customer’s problem,” “Dependencies between requirements are more a matter of fear than reality” and “Concentration is the Enemy.”

In between the chuckles, though, there is a serious analysis of XP’s many flaws. The authors also examine C3, the first XP project, whose team (most of whom went on to get XP book deals shortly before C3’s cancellation) described themselves as “the best team on the face of the Earth”. (In a later chapter, the authors also note that one problem which can affect pair programmers is overconfidence— or is that “eXcessive courage”?). The authors examine whether the problems that led to C3’s “inexplicable” cancellation could also afflict present-day XP projects.

In the final chapter (Refactoring XP) Matt and Doug suggest some ways of achieving the agile goals of XP using some XP practices (used in moderation) combined with other, less risk-laden methods.” –>

For more free books download visit this blog daily



Download









Book Details

•Paperback: 445 pages
•Publisher: Sybex (November 26, 2004)
•Language: English
•ISBN-10: 0782143512
•ISBN-13: 978-0782143515


Book Description

Have you tried using an “automated” GUI testing tool, only to find that you spent most of your time configuring, adjusting, and directing it?

This book presents a sensible and highly effective alternative: it teaches you to build and use your own truly automated tool. The procedure you’ll learn is suitable for virtually any development environment, and the tool allows you to store your test data and verification standard separately, so you can build it once and use it for other GUIs. Most, if not all, of your work can be done without test scripts, because the tool itself can easily be made to conduct an automatic GUI survey, collect test data, and generate test cases. You’ll spend virtually none of your time playing with the tool or application under test.
Code-intensive examples support all of the book’s instruction, which includes these key topics:

•Building a C# API text viewer
•Building a test monkey
•Developing an XML viewer using xPath and other XML-related classes
•Building complex, serializable classes for GUI test verification
•Automatically testing executable GUI applications and user-defined GUI controls
•Testing managed (.NET) and unmanaged GUI applications
•Automatically testing different GUI controls, including Label, TextBox, Button, CheckBox, RadioButton, Menu
•Verifying test results
Effective GUI Test Automation is the perfect complement to Li and Wu’s previous book, Effective Software Test Automation: Developing an Automated Software Testing Tool. Together, they provide programmers, testers, designers, and managers with a complete and cohesive way to create a smoother, swifter development process—and, as a result, software that is as bug-free as possible.

From the Back Cover
Have you tried using an “automated” GUI testing tool, only to find that you spent most of your time configuring, adjusting, and directing it?

This book presents a sensible and highly effective alternative: it teaches you to build and use your own truly automated tool. The procedure you’ll learn is suitable for virtually any development environment, and the tool allows you to store your test data and verification standard separately, so you can build it once and use it for other GUIs. Most, if not all, of your work can be done without test scripts, because the tool itself can easily be made to conduct an automatic GUI survey, collect test data, and generate test cases. You’ll spend virtually none of your time playing with the tool or application under test.

Code-intensive examples support all of the book’s instruction, which includes these key topics:

•Building a C# API text viewer
•Building a test monkey
•Developing an XML viewer using xPath and other XML-related classes
•Building complex, serializable classes for GUI test verification
•Automatically testing executable GUI applications and user-defined GUI controls
•Testing managed (.NET) and unmanaged GUI applications
•Automatically testing different GUI controls, including Label, TextBox, Button, CheckBox, RadioButton, Menu
•Verifying test results
For more free books download visit this blog daily



Download






Book Details

•Paperback: 400 pages
•Publisher: Sybex; 1 edition (February 19, 2004)
•Language: English
•ISBN-10: 0782143202
•ISBN-13: 978-0782143201


Book Description




“If you’d like a glimpse at how the next generation is going to program, this book is a good place to start.”
—Gregory V. Wilson, Dr. Dobbs Journal (October 2004)

Build Your Own Automated Software Testing Tool

Whatever its claims, commercially available testing software is not automatic. Configuring it to test your product is almost as time-consuming and error-prone as purely manual testing.

There is an alternative that makes both engineering and economic sense: building your own, truly automatic tool. Inside, you’ll learn a repeatable, step-by-step approach, suitable for virtually any development environment. Code-intensive examples support the book’s instruction, which includes these key topics:

•Conducting active software testing without capture/replay
•Generating a script to test all members of one class without reverse-engineering
•Using XML to store previously designed testing cases
•Automatically generating testing data
•Combining Reflection and CodeDom to write test scripts focused on high-risk areas
•Generating test scripts from external data sources
•Using real and complete objects for integration testing
•Modifying your tool to test third-party software components
•Testing your testing tool
Effective Software Test Automation goes well beyond the building of your own testing tool: it also provides expert guidance on deploying it in ways that let you reap the greatest benefits: earlier detection of coding errors, a smoother, swifter development process, and final software that is as bug-free as possible. Written for programmers, testers, designers, and managers, it will improve the way your team works and the quality of its products.

From the Back Cover

“If you’d like a glimpse at how the next generation is going to program, this book is a good place to start.”
Gregory V. Wilson, Dr. Dobbs Journal (October 2004)

Build Your Own Automated Software Testing Tool

Whatever its claims, commercially available testing software is not automatic. Configuring it to test your product is almost as time-consuming and error-prone as purely manual testing.

There is an alternative that makes both engineering and economic sense: building your own, truly automatic tool. Inside, you’ll learn a repeatable, step-by-step approach, suitable for virtually any development environment. Code-intensive examples support the book’s instruction, which includes these key topics:

•Conducting active software testing without capture/replay
•Generating a script to test all members of one class without reverse-engineering
•Using XML to store previously designed testing cases
•Automatically generating testing data
•Combining Reflection and CodeDom to write test scripts focused on high-risk areas
•Generating test scripts from external data sources
•Using real and complete objects for integration testing
•Modifying your tool to test third-party software components
•Testing your testing tool
Effective Software Test Automation goes well beyond the building of your own testing tool: it also provides expert guidance on deploying it in ways that let you reap the greatest benefits: earlier detection of coding errors, a smoother, swifter development process, and final software that is as bug-free as possible. Written for programmers, testers, designers, and managers, it will improve the way your team works and the quality of its products.


For more free books download visit this blog daily


Download











Book Details

•Paperback: 240 pages
•Publisher: Prentice Hall PTR; 1 edition (May 15, 2003)
•Language: English
•ISBN-10: 0130093653
•ISBN-13: 978-0130093653


Writing LabVIEW software to perform a complex task is never easy—especially when those last-minute feature requests cause a complexity explosion in your system, forcing you to rework much of your code! Jon Conway and Steve Watts offer a better solution: LCOD-LabVIEW Component Oriented Design—which, for the first time, applies the theories and principles of software design to LabVIEW programming. The material is presented in a lighthearted, engaging manner that makes learning enjoyable, even if you’re not a computer scientist.

•LCOD software engineering techniques make your software more robust and better able to handle complexity—by making it simpler! Even large, industrial-grade applications become manageable.
•Design to embrace flexibility first, making changes and bug fixes much less painful
•Pragmatic discussion of the authors’ tried and tested techniques, written by—and for—working programmers
•Covers design principles; LCOD overview, implementation, and complementary techniques; engineering essentials; style issues; and more
•Complete with practical advice on requirements gathering, prototyping, user interface design, and rich with examples
•Work through an example LCOD project (all code included on companion Web site) to tie the lessons together
This book is intended for test engineers, system integrators, electronics engineers, software engineers, and other intermediate to advanced LabVIEW programmers. None of the methods discussed are complex, so users can benefit as soon as they are proficient with the syntax of LabVIEW.Go to the companion Web site located at http://author.phptr.com/watts/ for full source code and book updates.

About the Author

JON CONWAY has 20 years’ experience in writing software, with half of that in LabVIEW. His fieldsof expertise include real time, robotics, databases, DAQ, DSP, and multiple software languages andoperating systems; his idea for LCOD arose from his experience gained working on complex softwareprojects. Jon is a partner in Structured Software Design Consultants of Hampshire, UK.

STEVE WATTS has 15 years of experience in writing test software, and has been programming inLabVIEW for 6 years. His areas of expertise include OOD, the Yourdon methodology, CASE tools,electronics, lasers, switching system design, DAQ, statistical process control, databases, userinterface design, software engineering, as well as a variety of programming languages. Steve is apartner in Structured Software Design Consultants of Hampshire, UK.

For more free books download visit this blog daily



Download








Book Details


•Hardcover: 187 pages
•Publisher: Wiley (August 2, 2004)
•Language: English
•ISBN-10: 0471653942
•ISBN-13: 978-0471653943

Book Description

Praise for Detail Process Charting
“A must-read for any competitive organization, Detail Process Charting: Speaking the Language of Process provides a comprehensive, yet clear, explanation of how to utilize one of the most powerful tools available to improve work processes. [Graham] has successfully integrated the history, success stories, and wisdom of those in the field who have applied this time-tested tool.”
-Jim Denyes, Training Manager
Naval Occupational Safety and Health, and Environmental Training Center
Author, Work Smarter, Not Harder
“This book will be a valuable resource for all those interested in work simplification and its implementation. Excellent answers to the ‘who,’ ‘what,’ ‘when,’ ‘how,’ and ‘why’ of work simplification are provided in an understandable and very useful level of detail. Graham has obviously ‘been there, done that.’ “
-John A. Roberts III, Adjunct Professor
School of Business Administration, University of Dayton
“The keys to this approach . . . are the involvement of the workers and the simplicity of the charting approach. Even those participants who have never seen a process chart can almost instantly see how the process works, their role in it, and how it can be improved. This level of involvement means continuous buy-in, which significantly improves the chances of success. The emphasis on the document as the key process element and the ability to diagram the document to flow easily, rapidly, and clearly set this approach apart from all the others.”
-Fredric D. Heilbronner, Director of Systems Consulting, eForms
Digital Consulting & Software Services, Inc.
“Much has been written about charting and business systems analysis, but I have not seen anything as comprehensive and clear as Ben Graham’s book. Writing in simple, easy-to-follow language with plentiful illustrations and practical examples, this book takes the reader through the full spectrum of the charting process from initial analysis to managing charting libraries. This book is a must-have for all process improvement analysts and managers wanting to improve their organizational efficiency.”
-Robert Barnett, Managing Director
Robert Barnett and Associates Pty. Ltd.

Download Description

Praise for Detail Process Charting
“A must-read for any competitive organization, Detail Process Charting: Speaking the Language of Process provides a comprehensive, yet clear, explanation of how to utilize one of the most powerful tools available to improve work processes. [Graham] has successfully integrated the history, success stories, and wisdom of those in the field who have applied this time-tested tool.”
-Jim Denyes, Training Manager
Naval Occupational Safety and Health, and Environmental Training Center
Author, Work Smarter, Not Harder
“This book will be a valuable resource for all those interested in work simplification and its implementation. Excellent answers to the ‘who,’ ‘what,’ ‘when,’ ‘how,’ and ‘why’ of work simplification are provided in an understandable and very useful level of detail. Graham has obviously ‘been there, done that.’ “
-John A. Roberts III, Adjunct Professor
School of Business Administration, University of Dayton
“The keys to this approach . . . are the involvement of the workers and the simplicity of the charting approach. Even those participants who have never seen a process chart can almost instantly see how the process works, their role in it, and how it can be improved. This level of involvement means continuous buy-in, which significantly improves the chances of success. The emphasis on the document as the key process element and the ability to diagram the document to flow easily, rapidly, and clearly set this approach apart from all the others.”
-Fredric D. Heilbronner, Director of Systems Consulting, eForms
Digital Consulting & Software Services, Inc.
“Much has been written about charting and business systems analysis, but I have not seen anything as comprehensive and clear as Ben Graham’s book. Writing in simple, easy-to-follow language with plentiful illustrations and practical examples, this book takes the reader through the full spectrum of the charting process from initial analysis to managing charting libraries. This book is a must-have for all process improvement analysts and managers wanting to improve their organizational efficiency.”
-Robert Barnett, Managing Director
Robert Barnett and Associates Pty. Ltd.


For more free books download visit this blog daily

Download






book Details

•Paperback: 336 pages
•Publisher: Addison-Wesley Professional; 2 edition (August 12, 1995)
•Language: English
•ISBN-10: 0201835959
•ISBN-13: 978-0201835953
The classic book on the human elements of software engineering. Software tools and development environments may have changed in the 21 years since the first edition of this book, but the peculiarly nonlinear economies of scale in collaborative work and the nature of individuals and groups has not changed an epsilon. If you write code or depend upon those who do, get this book as soon as possible — from Amazon.com Books, your library, or anyone else. You (and/or your colleagues) will be forever grateful. Very Highest Recommendation.

book Description
No book on software project management has been so influential and so timeless as The Mythical Man-Month. Now 20 years after the publication of his book, Frederick P. Brooks, Jr. (best known as the “father of the IBM System 360″) revisits his original ideas and develops new thoughts and advice both for readers familiar with his work and for readers discovering it for the first time.

From the Inside Flap

To my surprise and delight, The Mythical Man-Month continues to be popular after twenty years. Over 250,000 copies are in print. People often ask which of the opinions and recommendations set forth in 1975 I still hold, and which have changed, and how. Whereas I have from time to time addressed that question in lectures, I have long wanted to essay it in writing.


Peter Gordon, now a Publishing Partner at Addison-Wesley, has been working with me patiently and helpfully since 1980. He proposed that we prepare an Anniversary Edition. We decided not to revise the original, but to reprint it untouched (except for trivial corrections) and to augment it with more current thoughts.

Chapter 16 reprints “No Silver Bullet: Essence and Accidents of Software Engineering,” a 1986 IFIPS paper that grew out of my experience chairing a Defense Science Board study on military software. My co-authors of that study, and our executive secretary, Robert L. Patrick, were invaluable in bringing me back into touch with real-world large software projects. The paper was reprinted in 1987 in the IEEE Computer magazine, which gave it wide circulation.

“No Silver Bullet” proved provocative. It predicted that a decade would not see any programming technique which would by itself bring an order-of-magnitude improvement in software productivity. The decade has a year to run; my prediction seems safe. “NSB” has stimulated more and more spirited discussion in the literature than has The Mythical Man-Month. Chapter 17, therefore, comments on some of the published critique and updates the opinions set forth in 1986.

In preparing my retrospective and update of The Mythical Man-Month, I was struck by how few of the propositions asserted in it have been critiqued, proven, or disproven by ongoing software engineering research and experience. It proved useful to me now to catalog those propositions in raw form, stripped of supporting arguments and data. In hopes that these bald statements will invite arguments and facts to prove, disprove, update, or refine those propositions, I have included this outline as Chapter 18.

Chapter 19 is the updating essay itself. The reader should be warned that the new opinions are not nearly so well informed by experience in the trenches as the original book was. I have been at work in a university, not industry, and on small-scale projects, not large ones. Since 1986, I have only taught software engineering, not done research in it at all. My research has rather been on virtual reality and its applications.

In preparing this retrospective, I have sought the current views of friends who are indeed at work in software engineering. For a wonderful willingness to share views, to comment thoughtfully on drafts, and to re-educate me, I am indebted to Barry Boehm, Ken Brooks, Dick Case, James Coggins, Tom DeMarco, Jim McCarthy, David Parnas, Earl Wheeler, and Edward Yourdon. Fay Ward has superbly handled the technical production of the new chapters.

I thank Gordon Bell, Bruce Buchanan, Rick Hayes-Roth, my colleagues on the Defense Science Board Task Force on Military Software, and, most especially, David Parnas for their insights and stimulating ideas for, and Rebekah Bierly for technical production of, the paper printed here as Chapter 16. Analyzing the software problem into the categories of essence and accident was inspired by Nancy Greenwood Brooks, who used such analysis in a paper on Suzuki violin pedagogy.

Addison-Wesley’s house custom did not permit me to acknowledge in the 1975 Preface the key roles played by their staff. Two persons’ contributions should be especially cited: Norman Stanton, then Executive Editor, and Herbert Boes, then Art Director. Boes developed the elegant style, which one reviewer especially cited: “wide margins, and imaginative use of typeface and layout.” More important, he also made the crucial recommendation that every chapter have an opening picture. (I had only the Tar Pit and Rheims Cathedral at the time.) Finding the pictures occasioned an extra year’s work for me, but I am eternally grateful for the counsel.

Deo soli gloria or Soli Deo Gloria — To God alone be the glory.

Chapel Hill, N.C., F.

For more free books download visit this blog daily



Download

OR

Download

OR

Download

OR

Download

OR

Download

OR

Download


.





Book Details

Paperback: 350 pages
Publisher: Charles River Media; 1 edition (November 18, 2003)
Language: English
ISBN-10: 1584502460
ISBN-13: 978-1584502463



Book Description
Applied Software Engineering with Apache Jakarta Commons is a software engineering based guide to the Apache Jakarta Commons components (e.g., Betwixt, Digester, Discovery, Collections), other Apache projects such as Ant, the Axis Web Service toolkit, and the popular JUnit framework. The book emphasis focuses on solutions to complex problems using a simple task-driven approach. In this task-driven approach, the idea is to define a generic problem, for example Java class instantiation, and then provide solutions in multiple contexts, such as Collections-based factories, the Discovery package, or even the Launcher package. The book includes a companion CD-ROM with samples and source code.

Book Info
Text shows how to utilize Apache Jakarta and Open Source technologies to create commercial-quality business applications. CD-ROM contains source code and projects. Softcover. DLC: Software engineering.



For more free books download visit this blog daily


Download








.