It is gatherring of the information about the particular problem.information system analysis used for various phase. It is helpful for accomplish the activities and tasks more easily, efficiently.

To provide an Information System analysis are Imagine that you have decided to renovate your house. You have met with an architect and agreed on some basic concepts, time and cost estimates. Your family has approved these costs in the form of a “business case”.

Now imagine that you let the tradesmen start work—They have no real idea of what you require in sufficient detail to start renovations. Even with the best of intentions it is unlikely they will construct something that meets your requirements, and cost estimates.

Information management projects are similar--Requirements should be identified first, and approved by the business owner, before technical design begins. This way, the business owner is involved in “sign-off” of the requirements. The technical team is also involved with specifying requirements so they are in a better position to understand what is needed.

Just to clarify your question, is it that this system/app already exists, and you are being asked to provide details about its internal processes? Or is this a new application?

Thanks doctors C K Gomathy and Kgs Venkatesan for your valuable answers.

Dear Charles,

The application is new and I want to prepare a full road map for the project that contain 4 applications and I must analyse the information systems in a full study.

Thanks in advance

Hi Ahmed Meri , I If you are thinking what your system should do, you must first come up with a requirement specification. This can even have the wireframes (mocks) of user interfaces. There are various templates for user requirements specifications. IEEE format is a standard template (https://web.cs.dal.ca/~hawkey/3130/srs_template-ieee.doc). Even you can draw and use uml use-case diagrams (or activity diagrams, flow charts) to analyse and understand the system in study.

Please ask me in case if you need more info.

I would start using the Android architecture definition as a foundation and then detailing it in a list of the precise NVR (Name-Version-Release) of each library, application and component in each particular OS version. Probably you'll want consider to collect system configuration defaults and customizations too.

For practical examples check telemetry reports widely used. I'm thinking now in the ABRT system but there should be zillions of these and probably some Android specific.

For another perspective Ansible tools works collecting an massive description of the managed system. Very verbose but exhaustive.

Ahmed, I did a search on "system analysis report" and the first example is of a working system. I personally had never seen a report like this one, but I include it here for completeness. https://www.emerson.com/documents/automation/manuals-guides-guardian-sample-system-analysis-report-pss-en-67944.pdf

Then, I found something that might be used in any situation. It is a rather comprehensive and broad document template that at first glance looks fairly good. https://www.ogcio.gov.hk/en/our_work/infrastructure/methodology/system_development/doc/G61c_Effective_SAnD_Guide_Appendix_C_v1_1.pdf

I agree with others on this thread that requirements is where one normally starts when building a new system of any type. But it is more than that of course. What SDLC methodology you select for your project will influence the deliverables you and your team will need to prepare.

That said, focusing on what a system analysis report might include for an android project, this website has some templates that might be useful for you. https://clearbridgemobile.com/how-to-build-a-mobile-app-requirements-document/

Finally, I did come across a list of software development deliverable templates that I think would be useful for any project, especially those employing the waterfall approach. https://eas.rutgers.edu/?ht_kb=system-project-templates-sdlc

I will poke around a little more, and if I find anything else I will post it. Hope that helps somewhat.

Information systems analysis and design is a method used by companies ranging from IBM to PepsiCo to Sony to create and maintain information systems that perform basic business functions such as keeping track of customer names and addresses, processing orders, and paying employees. The main goal of systems analysis and design is to improve organizational systems, typically through applying software that can help employees accomplish key business tasks more easily and efficiently. As a systems analyst, you will be at the center of developing this software.